public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "matt at use dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/51986] New: [4.7 regression] uninitialized variable warning regression prevents bootstrap
Date: Tue, 24 Jan 2012 22:36:00 -0000 [thread overview]
Message-ID: <bug-51986-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51986
Bug #: 51986
Summary: [4.7 regression] uninitialized variable warning
regression prevents bootstrap
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: matt@use.net
This just started in the last few days:
/tmp/gcc-obj/./prev-gcc/g++ -B/tmp/gcc-obj/./prev-gcc/
-B/home/matt/x86_64-unknown-linux-gnu/bin/ -nostdinc++
-B/tmp/gcc-obj/prev-x86_64-unknown-linux-gnu/libstdc++-v3/src/.libs
-B/tmp/gcc-obj/prev-x86_64-unknown-linux-gnu/libstdc++-v3/libsupc++/.libs
-I/tmp/gcc-obj/prev-x86_64-unknown-linux-gnu/libstdc++-v3/include/x86_64-unknown-linux-gnu
-I/tmp/gcc-obj/prev-x86_64-unknown-linux-gnu/libstdc++-v3/include
-I/home/matt/src/gcc-4.7.0/libstdc++-v3/libsupc++
-L/tmp/gcc-obj/prev-x86_64-unknown-linux-gnu/libstdc++-v3/src/.libs
-L/tmp/gcc-obj/prev-x86_64-unknown-linux-gnu/libstdc++-v3/libsupc++/.libs -c
-g -O2 -flto=jobserver -frandom-seed=1 -O2 -finline-functions -funswitch-loops
-fpredictive-commoning -fgcse-after-reload -ftree-vectorize -ffast-math
-floop-interchange -floop-strip-mine -floop-block -ftree-loop-distribution
-ftree-loop-distribute-patterns -ftree-loop-im -ftree-loop-ivcanon -fivopts
-fweb -DIN_GCC -fno-exceptions -fno-rtti -W -Wall -Wno-narrowing
-Wwrite-strings -Wcast-qual -Wmissing-format-attribute -pedantic -Wno-long-long
-Wno-variadic-macros -Wno-overlength-strings -Werror -fno-common
-DHAVE_CONFIG_H -I. -I. -I/home/matt/src/gcc-4.7.0/gcc
-I/home/matt/src/gcc-4.7.0/gcc/. -I/home/matt/src/gcc-4.7.0/gcc/../include
-I/home/matt/src/gcc-4.7.0/gcc/../libcpp/include
-I/home/matt/src/gcc-4.7.0/gcc/../libdecnumber
-I/home/matt/src/gcc-4.7.0/gcc/../libdecnumber/bid -I../libdecnumber
/home/matt/src/gcc-4.7.0/gcc/sched-deps.c -o sched-deps.o
/home/matt/src/gcc-4.7.0/gcc/sched-deps.c: In function
‘sched_get_condition_with_rev(rtx_def const*, bool*)’:
/home/matt/src/gcc-4.7.0/gcc/sched-deps.c:599:33: error: ‘tmp’ may be used
uninitialized in this function [-Werror=maybe-uninitialized]
Verified that it is a false positive, as
sched_get_condition_with_rev_uncached() always sets the contents of the bool in
question (if it isn't NULL, and it isn't in this case).
Can be reduced to -O2 -finline-functions, which probably isn't getting tested
much since using the bootstrap-O3 config has been broken for months now.
Pre-processed sources are attached.
next reply other threads:[~2012-01-24 22:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 22:36 matt at use dot net [this message]
2012-01-24 22:40 ` [Bug middle-end/51986] " matt at use dot net
2012-01-25 10:57 ` rguenth at gcc dot gnu.org
2012-01-25 14:46 ` jakub at gcc dot gnu.org
2012-01-25 20:35 ` jakub at gcc dot gnu.org
2012-01-25 21:15 ` jakub 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-51986-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).