https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109442
--- Comment #3 from Jonathan Wakely ---
Ah, maybe the problem is that the library code manually elides destroying the
elements, precisely because it's a no-op. So we don't actually destroy the
elements, which means the compiler might think
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109442
--- Comment #2 from Jonathan Wakely ---
Neither v nor v1 escapes the function, so I don't think operator delete can
inspect them.
The destructor doesn't inspect the contents, it just destroys the elements
(which is a no-op for int) and then
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109442
Richard Biener changed:
What|Removed |Added
Keywords||missed-optimization
