------- Comment #2 from j at uriah dot heep dot sax dot de 2006-08-14 14:13 ------- I know that the current situation for the AVR is suboptimal, there really are overrides in libm.a for functions that are already present in libgcc.a. However, this is not so easy to change for a number of logistical reasons (the functions in question are highly tied into the remaining FP library framework, but they offer much more optimal code for the user).
However, the main question here is: shouldn't all user-supplied -lXXX options *always* be processed before any internally added -lgcc options, and why is the behaviour different when the user calls the compiler "avr-g++" rather than "avr-gcc"? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28718
