public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/52028] New: [4.7 Regression] wrong code with -O2 -ftree-loop-distribution
Date: Sat, 28 Jan 2012 16:40:00 -0000 [thread overview]
Message-ID: <bug-52028-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52028
Bug #: 52028
Summary: [4.7 Regression] wrong code with -O2
-ftree-loop-distribution
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: zsojka@seznam.cz
Host: x86_64-pc-linux-gnu
Target: x86_64-pc-linux-gnu
Created attachment 26489
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26489
reduced testcase
Compiler output:
$ gcc -O2 -ftree-loop-distribution testcase4.c
$ valgrind -q ./a.out
==32144== Conditional jump or move depends on uninitialised value(s)
==32144== at 0x4C2D333: bcmp (in
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==32144== by 0x4005F4: main (in /home/smatz/gcc-bug/1063/a.out)
==32144==
==32144== Conditional jump or move depends on uninitialised value(s)
==32144== at 0x4005F7: main (in /home/smatz/gcc-bug/1063/a.out)
==32144==
Aborted
Tested revisions:
r183666 - fail
r180540 - fail
r178498 - fail
4.6 r180325 - OK
next reply other threads:[~2012-01-28 14:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-28 16:40 zsojka at seznam dot cz [this message]
2012-01-28 16:48 ` [Bug tree-optimization/52028] " dominiq at lps dot ens.fr
2012-01-28 16:52 ` jakub at gcc dot gnu.org
2012-01-30 10:51 ` rguenth at gcc dot gnu.org
2012-01-30 14:13 ` rguenth at gcc dot gnu.org
2012-01-30 14:28 ` rguenth at gcc dot gnu.org
2012-01-30 16:17 ` rguenth at gcc dot gnu.org
2012-01-30 16:39 ` 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-52028-4@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).