https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101523
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to fail| |14.0
Ever confirmed|0 |1
Last reconfirmed| |2024-03-22
Status|UNCONFIRMED |NEW
--- Comment #42 from Richard Biener <rguenth at gcc dot gnu.org> ---
I checked with a cross btw, and with -O1 we use 10s and 900MB memory for the
testcase for comment #22. With -O2 it's 160s and 11GB as reported.
It might of course that with -O1 we simply do not confront combine with
the opportunity to blow up.
So IMHO this is a non-issue and the reporter should use -O1 for such a TU.
Still confirmed as a s390x specific problem and confirmed on trunk.
Statistics with the -O2 combines:
305 combine "successes" 9425
305 combine "three-insn combine" 1
305 combine "four-insn combine" 1
305 combine "merges" 40418007
305 combine "extras" 9110287
305 combine "two-insn combine" 9423
305 combine "attempts" 40440004
With -O1:
305 combine "successes" 1861
305 combine "three-insn combine" 1732
305 combine "merges" 191051
305 combine "extras" 9274
305 combine "two-insn combine" 129
305 combine "attempts" 192434
