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++/107555] Never constructed object destroyed during exception handling Date: Tue, 08 Nov 2022 17:07:42 +0000 [thread overview] Message-ID: <bug-107555-4-3JauM8bBCi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107555-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107555 --- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Boris Kolpackov from comment #6) > I was under the impression that only something runnable would be useful, but https://gcc.gnu.org/bugs/#need > if all that's need is a preprocessed translation unit, then that's no > problem at all. I've also attached the translation unit with the workaround > for your reference. Thanks for attaching them.
prev parent reply other threads:[~2022-11-08 17:07 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-07 13:34 [Bug c++/107555] New: " boris at kolpackov dot net 2022-11-08 9:28 ` [Bug c++/107555] " rguenth at gcc dot gnu.org 2022-11-08 9:47 ` boris at kolpackov dot net 2022-11-08 10:47 ` redi at gcc dot gnu.org 2022-11-08 13:12 ` boris at kolpackov dot net 2022-11-08 13:12 ` boris at kolpackov dot net 2022-11-08 13:21 ` boris at kolpackov dot net 2022-11-08 16:59 ` pinskia at gcc dot gnu.org 2022-11-08 17:07 ` redi at gcc dot gnu.org [this message]
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-107555-4-3JauM8bBCi@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).