https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79191
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed|2017-08-28 00:00:00 |2023-5-11
--- Comment #8 from Andrew Pin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79191
--- Comment #7 from Andrew Macleod ---
(In reply to Andrew Macleod from comment #6)
> Ranger knows the range of m_3 on entry to BB3 is:
> [0, 2][4294967296, 18446744069414584322]
> we cant enumerate all the ranges that have [0,2] in the lower wo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79191
Andrew Macleod changed:
What|Removed |Added
CC||amacleod at redhat dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79191
--- Comment #5 from Marc Glisse ---
(In reply to Eric Gallager from comment #4)
> Where exactly in the compiler is this optimization supposed to be done and
Eric, that's part of the problem. The optimization already exists in VRP, but
it is defe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79191
--- Comment #4 from Eric Gallager ---
Where exactly in the compiler is this optimization supposed to be done and
who's the maintainer of that file?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79191
--- Comment #3 from Eric Gallager ---
(In reply to Eric Gallager from comment #2)
> When I add an explicit "-m64" to the compile command I get the same results
> as you, though. Also, it'd be nice if there were a warning from -Wconversion
> for t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79191
Eric Gallager changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79191
Martin Sebor changed:
What|Removed |Added
Keywords||missed-optimization
See Also|
