Hi,
I have noted problem where gcc is optimizing if-then-else constructs -
with disastrous results. For example:
if (a >= 0)
return 8;
else
return 0;
(This is now reported as bug.)
Can folks try the following gcc option
-fno-if-conversion
on their own code at -Os optimization, and see if this produce
better/worse or same code? This will help figure if the whole pass
should be skipped - or whether it still contains useful optimizations.
Andy
_______________________________________________
AVR-GCC-list mailing list
AVR-GCC-list@nongnu.org
http://lists.nongnu.org/mailman/listinfo/avr-gcc-list
