https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65424
Sam James changed:
What|Removed |Added
CC||sjames at gcc dot gnu.org
--- Comment #6 fro
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65424
Pavel I. Kryukov changed:
What|Removed |Added
CC||pavel.kryukov at phystech dot
edu
--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65424
Andrew Pinski changed:
What|Removed |Added
CC||pinskia at gcc dot gnu.org
Sev
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65424
--- Comment #4 from Robert Clausecker ---
Sorry, comment was posted to the wrong bug. I have trouble using your
bug reporting software, the “automatically go to next bug after making
a change” behaviour is weird and unintuitive.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65424
--- Comment #3 from Robert Clausecker ---
I checked this again on a computer with more RAM and compilation does indeed
terminate
after 23 minutes. On the original machine, the compiler most likely swapped a
lot contrary
to my original report in w
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65424
--- Comment #2 from Robert Clausecker ---
I'm looking forwards to a fix! This optimization is important for me.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65424
Richard Biener changed:
What|Removed |Added
Keywords||missed-optimization
Status|
