public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "davidledger at live dot com.au" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/98401] Temporaries passed to co_await sometimes cause an extraneous call to destructor at incorrect address Date: Thu, 10 Jun 2021 14:28:30 +0000 [thread overview] Message-ID: <bug-98401-4-KR88TgKpD7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98401-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98401 David Ledger <davidledger at live dot com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |davidledger at live dot com.au --- Comment #3 from David Ledger <davidledger at live dot com.au> --- I'm seeing the same double destructor: https://godbolt.org/z/8r8oGG4z5 This appears to have many equivilent: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98401 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99576 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100611
next prev parent reply other threads:[~2021-06-10 14:28 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-20 16:39 [Bug c++/98401] New: " brandt.milo2 at gmail dot com 2020-12-20 16:40 ` [Bug c++/98401] " brandt.milo2 at gmail dot com 2021-01-09 19:56 ` dpsicilia at gmail dot com 2021-06-10 14:28 ` davidledger at live dot com.au [this message] 2021-06-23 8:55 ` victor.burckel at gmail dot com 2021-11-06 5:07 ` [Bug c++/98401] coroutines: " pigman46 at gmail dot com 2021-12-28 4:02 ` brandt.milo2 at gmail dot com 2021-12-28 4:03 ` brandt.milo2 at gmail dot com 2021-12-28 4:04 ` brandt.milo2 at gmail dot com 2021-12-28 10:03 ` iains 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-98401-4-KR88TgKpD7@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).