RE: [avr-libc-dev] Re: [RFC] Unified ELF file

[Eric Weddington]

> -----Original Message-----
> From: Michael Hennebry [mailto:address@hidden
> Sent: Thursday, September 27, 2007 7:41 AM
> To: Eric Weddington
> Cc: 'Michael Hennebry'; 'Dave Hylands'; 'avr-libc-dev'
> Subject: RE: [avr-libc-dev] Re: [RFC] Unified ELF file
>
> On Thu, 27 Sep 2007, Eric Weddington wrote:
>
> > Oh? And how would non-default fuse value not produce
> surprises? Default fuse
> > values are known good values and can be looked up in the datasheet.
>
> ??
> How would a value specified by the user produce surprise?
> In case I wasn't clear, I was suggesting that in the absence
> of a user-specified value that failure, preferably with a
> useful error message, is better than a default.

If a user specifes lfuse and efuse, but not hfuse, how are they going to be
ordered by the linker script in memory? What gets put in the hole? The ELF
file is just a group of data. It requires a program to decide if there is an
error and to report one. The ELF file itself can't decide if there was an
error. And I'm not about to patch the compiler toolchain with custom code
that can't be committed upstream.


> > I'm not turning this into a bike-shed event. Patches welcome.
>
> What is a bike-shed event?

Google is your friend.