https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87680
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87680
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87680
--- Comment #5 from Richard Biener ---
I believe this bug (and other existing dups) are about the C++ FE for array
initializers not emitting a loop for initialization but an initializer for each
element. It does that via
;; Function constexpr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87680
--- Comment #4 from Corey Kosak ---
To my eye it doesn't seem to be related to exceptions or initializer lists, so
I don't think it's the same bug, but you all would know better than me.
When I look at the .s file I see a giant sequence of the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87680
--- Comment #3 from Jonathan Wakely ---
PR 70277 is the one I was thinking of, and there's PR 55402 too.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87680
--- Comment #2 from Jonathan Wakely ---
Yes, there are dups. IIRC the problem is that every element of the array
introduces a new try/finally block so that if one of the Foo objects throws an
exception, all the earlier elements in the array get
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87680
Richard Biener changed:
What|Removed |Added
Keywords||missed-optimization