[Bug c++/103843] Direct call to Desctructor is optimized out

[jakub at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103843

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|FIXED                       |INVALID
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Accessing the member after the containing variable has been destructed is
undefined behavior in C++, so when you do it, anything can happen, it can
format your disk, do nothing, crash, ...