[Bug tree-optimization/60540] Don't convert int to float when comparing int with float (double) constant

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60540 Andrew Pinski changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill

[Bug tree-optimization/60540] Don't convert int to float when comparing int with float (double) constant

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60540 --- Comment #14 from Andrew Pinski --- So the original case we do handle since r9-3447.

[Bug tree-optimization/60540] Don't convert int to float when comparing int with float (double) constant

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60540 Andrew Pinski changed: What|Removed |Added CC||gabravier at gmail dot com --- Comment

[Bug tree-optimization/60540] Don't convert int to float when comparing int with float (double) constant

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60540 Oleg Endo changed: What|Removed |Added Target|sh*-*-* | --- Comment #12 from Oleg Endo --- (In

[Bug tree-optimization/60540] Don't convert int to float when comparing int with float (double) constant

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60540 --- Comment #11 from Harald van Dijk --- (In reply to Rich Felker from comment #10) > On this particular target, and on every target of any modern > relevance, (float)16777217 has well-defined behavior. That was exactly the point of my original

[Bug tree-optimization/60540] Don't convert int to float when comparing int with float (double) constant

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60540 --- Comment #10 from Rich Felker --- GCC can choose the behavior for any undefined behavior it wants, and GCC absolutely can make transformations based on behaviors it guarantees or that Annex F guarantees on targets for which it implements the

[Bug tree-optimization/60540] Don't convert int to float when comparing int with float (double) constant

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60540 --- Comment #9 from Harald van Dijk --- (In reply to Rich Felker from comment #8) > So arguments about generality to non-Annex-F C > environments are not relevant to the topic here. The comment it was a reply to suggested (possibly

[Bug tree-optimization/60540] Don't convert int to float when comparing int with float (double) constant

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60540 --- Comment #8 from Rich Felker --- > Floating point types are not guaranteed to support infinity by the C standard Annex F (IEEE 754 alignment) does guarantee it, and GCC aims to implement this. This issue report is specific to target sh*-*-*

[Bug tree-optimization/60540] Don't convert int to float when comparing int with float (double) constant

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60540 --- Comment #7 from Harald van Dijk --- (In reply to Rich Felker from comment #6) > > Only if the int is out of float's range. > > float's range is [-INF,INF] (endpoints included). There is no such thing as > "out of float's range". Floating

[Bug tree-optimization/60540] Don't convert int to float when comparing int with float (double) constant

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60540 Rich Felker changed: What|Removed |Added CC||bugdal at aerifal dot cx --- Comment #6

[Bug tree-optimization/60540] Don't convert int to float when comparing int with float (double) constant

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60540 Andrew Pinski changed: What|Removed |Added Keywords||missed-optimization