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 10:47:13 +0000	[thread overview]
Message-ID: <bug-107555-4-13fx8RSSSj@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 #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Just the preprocessed .ii file for the one translation unit compile-rule.cxx is
all that's needed.

The bug reporting instructions don't say you have to minimise it (though that's
certainly preferred) but they do say we need the preprocessed source.

  parent reply	other threads:[~2022-11-08 10:47 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 [this message]
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

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-13fx8RSSSj@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: link
Be 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).