[Bug c/59424] Optimization issue on min/max

2016-08-03 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59424 Andrew Pinski changed: What|Removed |Added Keywords||missed-optimization Severity|n

[Bug c/59424] Optimization issue on min/max

2016-03-14 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59424 Richard Biener changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug c/59424] Optimization issue on min/max

2013-12-09 Thread jmvalin at jmvalin dot ca
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59424 --- Comment #3 from Jean-Marc Valin --- What's strange is that adding -ffast-math makes gcc use maxss on func3() too, even though it was already allowed to without -ffast-math. I had the same problem with absolute value, although in that case fabs

[Bug c/59424] Optimization issue on min/max

2013-12-09 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59424 --- Comment #2 from Richard Biener --- (In reply to Marek Polacek from comment #1) > I can observe the same behavior with trunk. > > For func2, we compute a < b ? a : b first and then call sqrtf on that, while > for func3 we have return a < b ? A

[Bug c/59424] Optimization issue on min/max

2013-12-09 Thread mpolacek at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59424 Marek Polacek changed: What|Removed |Added CC||mpolacek at gcc dot gnu.org --- Comment #