Re: @far directive not working as expected
- From: Hans-Bernhard Broeker <broeker@xxxxxxxxxxxxxxxxxxxxx>
- Date: 28 Feb 2006 09:46:17 GMT
cyberzl1@xxxxxxxxx <cyberzl1@xxxxxxxxx> wrote:
Here is a good one for you guys......(I would ask in comp.lang.c, but
not sure this is ANSI C and those guys get weird if it isn't STRICTLY C
related).
It's worse than "not strictly" C related --- it has basically nothing
to do with the programming language C at all. It has to do with
details of the the non-standard behaviour of a particular programming
toolchain. You don't seem to even have established whether it's the
compiler or the linker whose behaviour you object to.
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?
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:.
--
Hans-Bernhard Broeker (broeker@xxxxxxxxxxxxxxxxxxxxx)
Even if all the snow were burnt, ashes would remain.
.
- Follow-Ups:
- Re: @far directive not working as expected
- From: cyberzl1@xxxxxxxxx
- Re: @far directive not working as expected
- References:
- @far directive not working as expected
- From: cyberzl1@xxxxxxxxx
- @far directive not working as expected
- Prev by Date: Re: why does the lcd display so lag.
- Next by Date: Re: why does the lcd display so lag.
- Previous by thread: @far directive not working as expected
- Next by thread: Re: @far directive not working as expected
- Index(es):
Relevant Pages
|
