From: Greg Schafer <gschafer@zip.com.au>
To: gcc@gcc.gnu.org
Subject: GCC silently miscompiling code on x86
Date: Thu, 22 Aug 2002 15:53:00 -0000 [thread overview]
Message-ID: <20020823085400.A6375@tigers-lfs.nsw.bigpond.net.au> (raw)
Hello gcc hackers!
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?
http://gcc.gnu.org/ml/gcc-patches/2002-08/msg01170.html
http://gcc.gnu.org/ml/gcc-patches/2002-07/msg01561.html
Thanks in advance.
Greg
next reply other threads:[~2002-08-22 15:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-22 15:53 Greg Schafer [this message]
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
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=20020823085400.A6375@tigers-lfs.nsw.bigpond.net.au \
--to=gschafer@zip.com.au \
--cc=gcc@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).