http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50782
--- Comment #4 from Richard Guenther 2011-10-19
08:16:34 UTC ---
The interaction of the optimize attribute/pragma with inlining are
"interesting".
For some options we prohibit inlining (but only for the target attribute/pragma
I think), otherwise
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50782
--- Comment #3 from Ethan Tira-Thompson 2011-10-18
23:55:47 UTC ---
I figured out what I did differently, I did some 'minor cleanup' and moved n
out of the function scope. This actually changes the optimization results.
This is just for referen
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50782
--- Comment #2 from Ethan Tira-Thompson 2011-10-18
21:28:42 UTC ---
Argh, sorry for the spastic updates, but I checked again and I definitely have
these lines in my console history:
$ g++ test.cc -o test -Wall -g -O3 && ./test
100
111
But now I'
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50782
--- Comment #1 from Ethan Tira-Thompson 2011-10-18
21:16:23 UTC ---
I'm sorry, apparently I messed something up in my testing.
The output of -O3 is actually:
000
111
The output of -O0 is:
100
111
So the optimize attribute is being applied afte
