|
One option is to typedef a structure and have only
one variable. Since you would probably access that variable so it wwould not be
optimized away. Also you get a form of documentation of the EEPROM structure in
the typedef.
----- Original Message -----
Sent: Thursday, June 15, 2006 6:59
AM
Subject: [avr-chat] ?Optimized
eeprom?
'Evening.
It would seem that changing from -O0 to -Os
removes all unreferenced entires from my eeprom.hex file. Failing that
it still moves things around even if no unrefereced vars. Not good when
you are sticking things in places that are not explicitly defined and using
several firmware revs.. Some questions come to mind:
1) Did I
just forget to add something to the makefile to keep the optimization settings
from mucking with the eeprom?
2) Beyond using '__attribute__((section
(".eeprom")))', or just hardcoding an adress, is there a cleaner way to
specify, "I want X in the eeprom at location Y, refering to it in the code by
name Z"?
Thanks,
Steve
_______________________________________________
AVR-chat mailing
list
address@hidden
http://lists.nongnu.org/mailman/listinfo/avr-chat
|