I've submitted https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65740
___
AVR-GCC-list mailing list
AVR-GCC-list@nongnu.org
https://lists.nongnu.org/mailman/listinfo/avr-gcc-list
Another interesting data point or two:
1) This goes back to at least 4.7
2) It's not avr-specific (as you might begin to suspect, given
previous discussion.)
I can get the same sort of bad behavior out of gcc for x86:
BillW-MacOSX-2<10405> /sw/lib/gcc4.7/bin/g++-fsf-4.7 -c -Os -w foo.cpp
-fno-inli
On 9 April 2015 at 01:15, Bill Westfield wrote:
> Is there a way to get gcc to dump the settings of all the parameters
> and option settings after it's done parsing the command line?
That would be -fverbose-asm combined with -S or --save-temps;
this dumps the settings in the assembly output.
An
Hmm. Particularly interesting is this series of "Considering"
paragraphs. about 42 all together (one for each call to move3Servos()
in loop()?)
Considering void move3Servos(Servo, float, Servo, float, Servo, float,
float) with 87 size
to be inlined into void loop() in oiOSoul.ino:3
