http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50724
Ethan Tira-Thompson changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
Resolution|INVA
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50724
--- Comment #9 from Ethan Tira-Thompson 2011-10-14
20:07:41 UTC ---
Thanks, I think Michael hit the nail on the head for summarizing my intention,
I'm satisfied to file this as a feature request (although personally I'd still
call it a bug ;))
F
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50724
--- Comment #11 from Ethan Tira-Thompson 2011-10-14
22:07:44 UTC ---
Marc: is this code perusable? I'm curious because I expect either the
calculations may generate NaN or not at all. If they might and you even have
test cases to handle it, then
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50724
Ethan Tira-Thompson changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|INVALID
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50724
Ethan Tira-Thompson changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|INVALID
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50724
Ethan Tira-Thompson changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Component|middle-
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50724
Ethan Tira-Thompson changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|DUPLICA
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50724
Ethan Tira-Thompson changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|DUPLICA
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50724
Ethan Tira-Thompson changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|DUPLICA
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50724
Ethan Tira-Thompson changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|DUPLICA
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50724
--- Comment #31 from Ethan Tira-Thompson 2011-10-18
00:33:41 UTC ---
I don't see what the hurry is to close the bug while it's still under
discussion. I guess you guys just like hit that 'resolved' button before
you've actually committed any res
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50782
Bug #: 50782
Summary: optimize pragma not applying fast-math
Classification: Unclassified
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50724
--- Comment #35 from Ethan Tira-Thompson 2011-10-18
21:09:07 UTC ---
Thanks all for the info!
I should have realized there was literally an attribute/pragma called
'optimize' (duh), and it's already in the docs... for some reason I had gotten
th
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
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 #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
16 matches
Mail list logo