... I find in my system: /usr/lib/gcc-lib/m6811-elf/3.3.6-m68hc1x-20060122/mshort/mlong-calls/libgcc.a so it looks like all your mystery functions (which are

... Many thank yous; it's embarassing that I didn't notice that. I get so used to linking with gcc command. __________________________________________________

On Sat, 21 Oct 2006 07:43:50 +1000, Jefferson Smith ... That's gcc's command line. Either pass that to m6811-elf-ld, or m6811-elf-gcc

... This is a potential concern, given the frequency with which these functions are called, performance could be significantly impacted. This is why I was

... You considered converting these few/tiny functions into "far" types, but that doesn't sound like a desirable solution. Too large percent of the time would

I've been working on all the issues surrounding banking, and have solved the major problems, but have hit something I to which I can't find an answer. This

I can't get "--defsym" to work with ld according to http://m68hc11.serveftp.org/doc/ld_2.html#SEC2 I try m6811-elf-gcc -m68hcs12 -mshort -Wl,-T,ldscript-rom.x

... I wonder what it emits for *((volatile word*) &offset[_eeprom_base]) = 0; Mike -- p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);} This

... Ah, the offset. Makes it completely backwards? This is all messed up 8-P With the offset it works without -O and not with With no offset it works with -O

... Same version here (3.1). If you're saying -Os does not change it to clr-clr, are you sure you recompiled? Apparently it is the optimizer breaking it. It

... Here with -Os (I use version 3.1 of the tool-chain). But the size of my function was different. So we learn, don't rely on optimization. I wonder, if the

... It says it was fixed in 2.92. I have 3.1 and without -Os I get two 8bit accesses. Ah, the difference is the offset: // v 3.1 toolchain, gcc parameters

Oh no... the bugreport says it is fixed. I was right, he had agreed it was a bug. I didn't find it before because I only looked at bugreports still open.

... Yeah, I use LMA and VMA pretty easily now. It's not "relocatable", but just loads to a different address (Flash) than the address it expects to execute at.

... Yes I've had optimization enabled (-Os) because my extern inline functions did not compile correctly without it. So did you mean "Without -Os" it emits

Frank, I used a different approach that has allowed me to write C code and run it in RAM. I am using the MC9S12NE64 which has 4 16K Flash pages, with only 3

... Actually, this won't work, either, because it doesn't address the issue of an atomic, not just uninterruptible, 16 bit access. A specially-designed set of

... The problem with all such attempts to address this issue boils down to this: If the compiler changes, then the programmer has to go back and "fiddle around

... Do you have optimization enabled ? With -Os it does not emit the clr, but a movw #0,... instead. You might also do this: volatile word zero = 0; *(volatile

Thanks - I knew I could do it with assembly easier. I was kind of hoping to write the relocatable function in C, that's all. Any ideas which linker file