Re: @far directive not working as expected
- From: "cyberzl1@xxxxxxxxx" <cyberzl1@xxxxxxxxx>
- Date: 28 Feb 2006 06:08:59 -0800
toolchain. You don't seem to even have established whether it's theI am not sure, but I think it is the linker whose behaviour is causing
compiler or the linker whose behaviour you object to.
me trouble. It may be my syntax and/or the compiler. I really don't
know.
That is bad because I wanted it in far space. I tried to put in far
It is using 3 byte(ie far) addressing, BUT it stuck the bloody thing
in near space.
And why is that bad? Is that architecture of addressing functions as
"far" if they are in "near space"? Are you running out of "near"
space?
space for a reason. Near space is my limiting factor right now.
I am using a Motorolla 9s12DG128 with the cosmic compiler v 4.6a.
Now here's some information you really should have put a lot further
up in your post. Possibly in the Subject:.
OK, maybe should have been higher in the post. At least I included it.
.
- Follow-Ups:
- Re: @far directive not working as expected
- From: Hans-Bernhard Broeker
- Re: @far directive not working as expected
- References:
- @far directive not working as expected
- From: cyberzl1@xxxxxxxxx
- Re: @far directive not working as expected
- From: Hans-Bernhard Broeker
- @far directive not working as expected
- Prev by Date: Re: Embedded Job Opening in Big D
- Next by Date: Re: <INTEGRITY RTOS> Error "ObjectTableIsFull" while CreateProtectedTask()
- Previous by thread: Re: @far directive not working as expected
- Next by thread: Re: @far directive not working as expected
- Index(es):
Relevant Pages
|