> -----Original Message----- > From: Colin O'Flynn [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 02, 2007 4:49 PM > To: [email protected] > Cc: Eric Weddington > Subject: Re: [avr-libc-dev] [RFC] Unified ELF file > > Hi Eric, > > I'm applying your patches now, so will have more comments > once I get the > system working... > > But a quick question: what would you say to defining a macro > such you could > just do: > > FUSES = > { > .low = LFUSE_DEFAULT, > .high = HFUSE_DEFAULT, > .extended = EFUSE_DEFAULT, > }; > > Just as a convience to users? >
Hmm. Might be a good idea. I purposely chose the identifier __fuse_t (as an internal identifier) because I may want to add stuff later. Right now the attribute is "section" with the named section ".fuse". I'm thinking that it might be a good idea later on to create an AVR-specific attribute __fusemem__, like we now have __progmem__, which would put the data in the fuse memory. In doing the new attribute, then we can create fuse_t as a struct with the new attribute. I would rather do this kind of change later as it is more intrusive changes to the AVR port in GCC. With the existing patches, it just changes avr-libc. So in a sense, having a FUSES macro might be a good way to hide all the underlying stuff and any changes later on. Anyone else have thoughts on this? Thanks for taking a look at this Colin! :-) Eric Weddington _______________________________________________ AVR-libc-dev mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/avr-libc-dev
