public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
* [Bug c/51542] New: bootstrap failure due to uninitialized variable use in c-parser @ 2011-12-14 0:36 matt at use dot net 2011-12-14 5:19 ` [Bug c/51542] " d.g.gorbachev at gmail dot com ` (2 more replies) 0 siblings, 3 replies; 4+ messages in thread From: matt at use dot net @ 2011-12-14 0:36 UTC (permalink / raw) To: gcc-bugs 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] ^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug c/51542] bootstrap failure due to uninitialized variable use in c-parser 2011-12-14 0:36 [Bug c/51542] New: bootstrap failure due to uninitialized variable use in c-parser matt at use dot net @ 2011-12-14 5:19 ` 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 2 siblings, 0 replies; 4+ messages in thread From: d.g.gorbachev at gmail dot com @ 2011-12-14 5:19 UTC (permalink / raw) To: gcc-bugs http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51542 --- Comment #1 from Dmitry Gorbachev <d.g.gorbachev at gmail dot com> 2011-12-14 05:17:04 UTC --- PR 50148. ^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug c/51542] bootstrap failure due to uninitialized variable use in c-parser 2011-12-14 0:36 [Bug c/51542] New: bootstrap failure due to uninitialized variable use in c-parser matt at use dot net 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 2 siblings, 0 replies; 4+ messages in thread From: marc.glisse at normalesup dot org @ 2011-12-14 22:27 UTC (permalink / raw) To: gcc-bugs http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51542 Marc Glisse <marc.glisse at normalesup dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marc.glisse at normalesup | |dot org --- Comment #2 from Marc Glisse <marc.glisse at normalesup dot org> 2011-12-14 22:22:41 UTC --- And PR 44938 before that. ^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug c/51542] bootstrap failure due to uninitialized variable use in c-parser 2011-12-14 0:36 [Bug c/51542] New: bootstrap failure due to uninitialized variable use in c-parser matt at use dot net 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 2 siblings, 0 replies; 4+ messages in thread From: matt at use dot net @ 2012-01-23 20:04 UTC (permalink / raw) To: gcc-bugs http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51542 --- Comment #3 from Matt Hargett <matt at use dot net> 2012-01-23 19:16:12 UTC --- As I mentioned in the other bug, the specific optimization from -O3 that triggers this if -fipa-cp-clone. Is there a reason these patches haven't been applied? Bootstrapping the compiler with -O3 is a great way to test and find issues before a release, but it's not feasible right now due to this issue. At the very least, since it has been reproduced and acknowledged, can the status be upgraded from 'unconfirmed'? ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2012-01-23 19:16 UTC | newest] Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2011-12-14 0:36 [Bug c/51542] New: bootstrap failure due to uninitialized variable use in c-parser matt at use dot net 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
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).