[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [avr-libc-dev] program space

From: Florian Bantner
Subject: Re: [avr-libc-dev] program space
Date: Fri, 4 Mar 2005 14:13:42 +0100
User-agent: Mutt/1.3.28i

Same thing here. Managed to put Strings in PG (with Help from here) but 
failed with a b-tree. How to put into and access something like node.right
in PG? Don't know. How to declare a Pointer to a struct in PG? Don't
know either. Documentation? Nothing. But it's for GCC-List. libc
can't do anything.

On Fre, 04 Mär 2005, Curtis Maloney wrote:

> I realise this is more something for the gcc side of things, however...
> Today at work I was trying to migrate some CodeVisionAVR code to GCC. 
> CV makes it trivial to store stuff in EEPROM or FLASH, you just use the 
> appropriate modifies on the variable declaration.
> Of course, in the "non-target-specific" world of GCC, things are a 
> little different.  But when trying to specify that a structure was in 
> code space, I just could not achieve it.  I tried everything I could 
> think of, but it just wouldn't work right.
> And now I'm trying to move some big const tables into code space, 
> instead of ram, so I can use my code on an 8535, but it requires making 
> some significant changes to the test of my code to make it reference the 
> code space.
> Now, what I'm wondering is why can't some special attribute on vars be 
> passed through to the back end so it a)puts it in .text, and b)knows to 
> generate code-space accesses?
> Or have I missed something fundamental?
> --
> Curtis Maloney
> _______________________________________________
> AVR-libc-dev mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/avr-libc-dev

Florian Bantner                 fon +49 (0)941 599 854 4
AXON-E interaktive medien       fax +49 (0)941 599 854 1
technische Leitung              mail address@hidden
                                web http://www.axon-e.de
gpg public key    http://www.axon-e.de/gpg/f.bantner.key
hash  1191 0C87 D9DB 3217 ABBA  5223 6D74 AB19 5C9D FC49

reply via email to

[Prev in Thread] Current Thread [Next in Thread]