public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/103843] Direct call to Desctructor is optimized out Date: Mon, 27 Dec 2021 16:38:03 +0000 [thread overview] Message-ID: <bug-103843-4-2FtyLp0H2c@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103843-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103843 --- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> --- Also, this is an automatic (i.e. stack) variable, so the destructor will run at the end of the block, meaning it will be settled twice. So another form of undefined behaviour. The program is just broken, in multiple ways. You cannot expect sensible behaviour from garbage code.
next prev parent reply other threads:[~2021-12-27 16:38 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-27 9:21 [Bug c++/103843] New: " georgii.shagov@be-tse.de 2021-12-27 9:33 ` [Bug c++/103843] " georgii.shagov@be-tse.de 2021-12-27 9:38 ` pinskia at gcc dot gnu.org 2021-12-27 9:44 ` georgii.shagov@be-tse.de 2021-12-27 9:51 ` pinskia at gcc dot gnu.org 2021-12-27 12:03 ` georgii.shagov@be-tse.de 2021-12-27 12:08 ` jakub at gcc dot gnu.org 2021-12-27 16:38 ` redi at gcc dot gnu.org [this message] 2021-12-27 16:41 ` redi at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-103843-4-2FtyLp0H2c@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).