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 c/51542] New: bootstrap failure due to uninitialized variable use in c-parser
Date: Wed, 14 Dec 2011 00:36:00 -0000	[thread overview]
Message-ID: <bug-51542-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51542

             Bug #: 51542
           Summary: bootstrap failure due to uninitialized variable use in
                    c-parser
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: matt@use.net


I checked by hand, and this looks real to me. It doesn't come up without
-O[3,fast] and LTO probably due to a lack of inlining that limits visibility of
the analysis.

NOTE: I have hand-modified my build/bootstrap-lto.mk to use -Ofast

$ ~/src/gcc-trunk/configure --enable-bootstrap --prefix=/home/matt
--enable-clocale=gnu --with-system-zlib --with-demangler-in-ld --enable-lto
--with-fpmath=sse --enable-languages=c,c++,lto
--with-build-config=bootstrap-lto --enable-build-with-cxx --disable-libmudflap
--with-cpu=core2 --with-tune=core2 --disable-libssp

$ make -j7 profiledbootstrap

/home/matt/src/gcc-trunk/gcc/c-parser.c: In function ‘c_expr
c_parser_postfix_expression_after_primary(c_parser*, location_t, c_expr)’:
/home/matt/src/gcc-trunk/gcc/c-parser.c:6880:16: error: ‘origtypes’ may be used
uninitialized in this function [-Werror=maybe-uninitialized]


             reply	other threads:[~2011-12-14  0:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-14  0:36 matt at use dot net [this message]
2011-12-14  5:19 ` [Bug c/51542] " d.g.gorbachev at gmail dot com
2011-12-14 22:27 ` marc.glisse at normalesup dot org
2012-01-23 20:04 ` matt at use dot net

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-51542-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).