public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "andi-gcc at firstfloor dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/61969] [4.8/4.9/5 Regression] wrong code by LTO on i?86-linux-gnu (affecting trunk, 4.9.x, and 4.8.x)
Date: Sun, 28 Sep 2014 06:07:00 -0000 [thread overview]
Message-ID: <bug-61969-4-YWkxRmm6Ka@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61969-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61969
Andi Kleen <andi-gcc at firstfloor dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |andi-gcc at firstfloor dot org
--- Comment #3 from Andi Kleen <andi-gcc at firstfloor dot org> ---
I did some experiments. I can reproduce it with trunk for 32bit.
The interesting part is that the printed value seems to be uninitialized on the
stack and changes on every run. a valgrind run gives
=23130== Use of uninitialised value of size 4
==23130== at 0x40B102B: _itoa_word (in /lib/libc-2.18.so)
==23130== by 0x40B474A: vfprintf (in /lib/libc-2.18.so)
==23130== by 0x40BAFCE: printf (in /lib/libc-2.18.so)
==23130== by 0x40879D2: (below main) (in /lib/libc-2.18.so)
==23130== Uninitialised value was created by a stack allocation
==23130== at 0x80482F4: main (in /home/andi/Downloads/pr61969/t)
==23130==
... more warnings like this ...
next prev parent reply other threads:[~2014-09-28 6:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 20:46 [Bug lto/61969] New: wrong code by LTO on x86_64-linux-gnu " su at cs dot ucdavis.edu
2014-07-31 10:35 ` [Bug lto/61969] [4.8/4.9/4.10 Regression] wrong code by LTO on i?86-linux-gnu " rguenth at gcc dot gnu.org
2014-08-01 6:34 ` su at cs dot ucdavis.edu
2014-09-28 6:07 ` andi-gcc at firstfloor dot org [this message]
2014-09-28 6:23 ` [Bug lto/61969] [4.8/4.9/5 " andi-gcc at firstfloor dot org
2014-09-28 6:35 ` andi-gcc at firstfloor dot org
2014-10-07 14:15 ` andi-gcc at firstfloor dot org
2014-10-07 14:35 ` rguenth at gcc dot gnu.org
2014-10-07 17:53 ` andi at firstfloor dot org
2014-10-08 1:46 ` andi-gcc at firstfloor dot org
2014-10-08 14:36 ` rguenth at gcc dot gnu.org
2014-10-09 8:22 ` rguenth at gcc dot gnu.org
2014-10-09 8:22 ` [Bug lto/61969] [4.8/4.9 " rguenth at gcc dot gnu.org
2014-11-26 13:15 ` [Bug lto/61969] [4.8 " rguenth at gcc dot gnu.org
2014-11-26 13:16 ` rguenth at gcc dot gnu.org
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=bug-61969-4-YWkxRmm6Ka@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).