[Bug other/55312] New: libbacktrace doesn't honor --disable-werror

[markus at trippelsdorf dot de]

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: unassig...@gcc.gnu.org
        ReportedBy: mar...@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;