From: "H. J. Lu" <hjl@lucon.org>
To: Richard Henderson <rth@redhat.com>,
Greg Schafer <gschafer@zip.com.au>,
gcc@gcc.gnu.org
Subject: Re: GCC silently miscompiling code on x86
Date: Fri, 30 Aug 2002 21:25:00 -0000 [thread overview]
Message-ID: <20020830212552.A3281@lucon.org> (raw)
In-Reply-To: <20020829190443.GA549@redhat.com>
On Thu, Aug 29, 2002 at 12:04:43PM -0700, Richard Henderson wrote:
> On Fri, Aug 23, 2002 at 08:54:00AM +1000, Greg Schafer wrote:
> > This is very bad for i686. Many continue to get hit by this. H J Lu has
> > proposed some patches but they remain unreviewed. Could somebody kindly
> > take a look at these and get this sorted?
>
> As far as I can tell, HJ's patch doesn't work. Certainly
> it didn't change the output for the given test case at all.
I guess people may tell you otherwise.
>
> I have a different patch that I started some time ago before I
> left on vacation that fixes this bug, as well as the variable
> sized structure copy bug as seen in execute/20020412-1.c.
>
I am looking forward to it.
H.J.
prev parent reply other threads:[~2002-08-30 21:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-22 15:53 Greg Schafer
2002-08-22 19:38 ` H. J. Lu
2002-08-29 12:04 ` Richard Henderson
2002-08-29 15:03 ` Greg Schafer
2002-08-29 16:26 ` Richard Henderson
2002-08-30 21:25 ` H. J. Lu [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=20020830212552.A3281@lucon.org \
--to=hjl@lucon.org \
--cc=gcc@gcc.gnu.org \
--cc=gschafer@zip.com.au \
--cc=rth@redhat.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).