https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71769
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71769
--- Comment #6 from amker at gcc dot gnu.org ---
(In reply to nightstrike from comment #5)
> Could you backport to the branches?
Well, that's release manager's call. Richard?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71769
--- Comment #5 from nightstrike ---
Could you backport to the branches?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71769
amker at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71769
amker at gcc dot gnu.org changed:
What|Removed |Added
CC||amker at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71769
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71769
--- Comment #1 from nightstrike ---
Would this also be a missed optimization? If the warning is saying that it
can't optimize a loop, and the warning is invalid, then if the loop is
optimizable but isn't being optimized would that qualify