public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Jason Merrill <jason@redhat.com>
To: jason@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/5504: Optimization breaks wei-ku-1 from blitz
Date: Fri, 05 Apr 2002 15:16:00 -0000 [thread overview]
Message-ID: <20020405231601.27834.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/5504; it has been noted by GNATS.
From: Jason Merrill <jason@redhat.com>
To: Richard Henderson <rth@redhat.com>
Cc: Diego Novillo <dnovillo@redhat.com>, gcc@gcc.gnu.org,
gcc-gnats@gcc.gnu.org
Subject: Re: c++/5504: Optimization breaks wei-ku-1 from blitz
Date: Sat, 06 Apr 2002 00:08:11 +0100
>>>>> "Jason" == Jason Merrill <jason@redhat.com> writes:
> For 3.1, one option would be to go back to doing destructor cleanups only
> on the normal flow path; this would break EH semantics again for this case,
> but that would not be a regression and I don't think I've ever seen a bug
> report about it in past releases.
I take it back; PR c++/411 is for this bug. We may still want to do this,
though.
Jason
next reply other threads:[~2002-04-05 23:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-05 15:16 Jason Merrill [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-09 9:35 reichelt
2003-05-08 22:44 bangerth
2002-04-18 6:46 Jason Merrill
2002-04-10 10:42 rth
2002-04-05 15:26 Jason Merrill
2002-04-03 18:26 Diego Novillo
2002-04-03 18:08 jason
2002-03-26 6:46 Diego Novillo
2002-03-22 10:14 jakub
2002-03-22 10:10 jakub
2002-03-22 7:51 dnovillo
2002-03-21 7:12 jakub
2002-03-20 9:36 Peter Schmid
2002-03-18 7:02 jakub
2002-01-26 16:06 Peter Schmid
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=20020405231601.27834.qmail@sources.redhat.com \
--to=jason@redhat.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=jason@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).