From: Richard Henderson <rth@redhat.com>
To: Mark Mitchell <mark@codesourcery.com>
Cc: Jason Merrill <jason@redhat.com>,
Diego Novillo <dnovillo@redhat.com>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
"gcc-gnats@gcc.gnu.org" <gcc-gnats@gcc.gnu.org>
Subject: Re: PR c++/5504: Optimization breaks wei-ku-1 from blitz
Date: Sat, 06 Apr 2002 23:38:00 -0000 [thread overview]
Message-ID: <20020406230944.A1055@redhat.com> (raw)
In-Reply-To: <50920000.1018133334@gandalf.codesourcery.com>; from mark@codesourcery.com on Sat, Apr 06, 2002 at 02:48:54PM -0800
On Sat, Apr 06, 2002 at 02:48:54PM -0800, Mark Mitchell wrote:
> I think this is the most practical solution under the circumstances.
Hold off a bit. I don't think either of the solutions
that Jason suggests are hard to implement. I'd certainly
prefer a solution that doesn't re-introduce bugs...
r~
next prev parent reply other threads:[~2002-04-07 7:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-25 21:41 Diego Novillo
2002-04-03 18:04 ` Jason Merrill
2002-04-03 19:23 ` Diego Novillo
2002-04-05 15:08 ` Jason Merrill
2002-04-05 16:14 ` Jason Merrill
2002-04-06 15:36 ` PR " Mark Mitchell
2002-04-06 23:38 ` Richard Henderson [this message]
2002-04-09 0:20 ` Richard Henderson
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=20020406230944.A1055@redhat.com \
--to=rth@redhat.com \
--cc=dnovillo@redhat.com \
--cc=gcc-gnats@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=mark@codesourcery.com \
/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).