Re: [avr-chat] far addresses

[Bob von Knobloch]

On 31/08/17 20:26, Bill Gatliff wrote:

> It's inevitable that when data spills over into a memory space with a
> different access schema, a C compiler goes nuts: the machine abstraction
> that C is defined around supports no such concept. That's doubly so for a
> general-purpose compiler like gcc, where exceptions to those rules all have
> to be dealt with outside the compiler's main workflow.
Yes, that is the conclusion I had also come to.
I see that Bob Paddock's reply (that avr-gcc turns the output of '&' into a 16 
bit pointer) explains the limitation (but not the 'mangling' that I see).
And Rolf Pfister
"I had to create quite a lot of strings to get above the 64KB limit.
When having not too many the compiler put them at lower addresses
and program code will go to higher addresses. So most the time
it will not be a problem."

My system, however, set these specifically in high memory using a linker map. 
So this was a real problem.
Reorganisation has mitigated the problem for now.
Thanks to all who contributed.

Bob

--
The Sun is out, the sky is blue, it's time to drive the MR2.