This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug c/51542] New: bootstrap failure due to uninitialized variable use in c-parser


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]


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]