[Bug general/21011] "may be used uninitialized" error with -Werror=maybe-uninitialized

2017-04-24 Thread luizluca at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=21011 --- Comment #17 from Luiz Angelo Daros de Luca --- > Or your alternative glibc headers don't provide enough information about > assert to the compiler? musl dropped the attribute noreturn, which got reverted sometime after. http://www.openwa

Re: [PATCH v2] Add frame pointer unwinding for aarch64

2017-04-24 Thread Mark Wielaard
On Thu, 2017-04-20 at 14:41 +0200, Ulf Hermann wrote: > diff --git a/tests/backtrace.aarch64.fp.core.bz2 > b/tests/backtrace.aarch64.fp.core.bz2 > new file mode 100644 > index 000..ef628af > Binary files /dev/null and b/tests/backtrace.aarch64.fp.core.bz2 differ > diff --git a/tests/backtrace.

[Bug general/21011] "may be used uninitialized" error with -Werror=maybe-uninitialized

2017-04-24 Thread mark at klomp dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=21011 Mark Wielaard changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug general/21011] "may be used uninitialized" error with -Werror=maybe-uninitialized

2017-04-24 Thread mark at klomp dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=21011 --- Comment #15 from Mark Wielaard --- (In reply to Luiz Angelo Daros de Luca from comment #14) > I do not set -DNDEBUG. All compiler flags are similar in this case. Maybe a > gcc bug? Or your alternative glibc headers don't provide enough in