From: "H.J. Lu" <hjl.tools@gmail.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>, GCC Development <gcc@gcc.gnu.org>
Subject: GCC mainline is broken on x86
Date: Sun, 12 Jun 2011 14:00:00 -0000 [thread overview]
Message-ID: <BANLkTi=Oe1BuSWoSLLxii-jSk+uihiNSgw@mail.gmail.com> (raw)
Hi,
Revision 174952:
http://gcc.gnu.org/ml/gcc-cvs/2011-06/msg00441.html
totally breaks C++ on x86:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49378
http://gcc.gnu.org/ml/gcc-regression/2011-06/msg00159.html
One symptom is we are using uninitialized registers, which leads
to writing random memory location. The same ia32 binary works on
Fedora 14 under kernel 2.6.35 and failed under Fedora 15 under
kernel 2.6.38.
We also use uninitialized registers on x86-64, but the program
doesn't crash. This bug may also affects C and other languages.
--
H.J.
reply other threads:[~2011-06-12 13:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='BANLkTi=Oe1BuSWoSLLxii-jSk+uihiNSgw@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--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).