public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "markus at trippelsdorf dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/55312] New: libbacktrace doesn't honor --disable-werror Date: Tue, 13 Nov 2012 14:21:00 -0000 [thread overview] Message-ID: <bug-55312-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55312 Bug #: 55312 Summary: libbacktrace doesn't honor --disable-werror Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: other AssignedTo: unassigned@gcc.gnu.org ReportedBy: markus@trippelsdorf.de When gcc is configured with "--disable-werror" and then build with: % make -j4 BOOT_CFLAGS="-march=native -O3 -pipe" STAGE1_CFLAGS="-march=native -O3 -pipe" CFLAGS_FOR_TARGET="-march=native -O3 -pipe" CXXFLAGS_FOR_TARGET="-march=native -O3 -pipe" profiledbootstrap One gets: ... /home/markus/gcc/libbacktrace/dwarf.c: In function ‘build_address_map’: /home/markus/gcc/libbacktrace/dwarf.c:1387:13: error: ‘val.u.string’ may be used uninitialized in this function [-Werror=maybe-uninitialized] lineoff = val.u.uint; ... /home/markus/gcc/libbacktrace/dwarf.c: In function ‘read_referenced_name’: /home/markus/gcc/libbacktrace/dwarf.c:2078:36: error: ‘val.u.string’ may be used uninitialized in this function [-Werror=maybe-uninitialized] name = read_referenced_name (ddata, u, val.u.uint, ... checking ctype.h usability... /home/markus/gcc/libbacktrace/dwarf.c: In function ‘read_function_entry’: /home/markus/gcc/libbacktrace/dwarf.c:2329:22: error: ‘val.u.string’ may be used uninitialized in this function [-Werror=maybe-uninitialized] function->name = val.u.string;
next reply other threads:[~2012-11-13 14:21 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-13 14:21 markus at trippelsdorf dot de [this message] 2012-11-13 18:25 ` [Bug other/55312] " markus at trippelsdorf dot de 2012-11-13 21:26 ` ian at gcc dot gnu.org 2012-11-13 21:28 ` ian at airs dot com
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-55312-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: linkBe 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).