New: gcc5.4 buildroot toolchain for powerpc libsanitizer failure

https://bugs.busybox.net/show_bug.cgi?id=10061

Bug ID: 10061
Summary: gcc5.4 buildroot toolchain for powerpc libsanitizer
failure
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: matthew.weber at rockwellcollins.com
CC: buildroot at uclibc.org
Target Milestone: ---

I'm building the following Buildroot Custom toolchain config and noticing a libsanitizer failure.

../../../../libsanitizer/asan/asan_linux.cc: In function ?bool __asan::AsanInterceptsSignal(int)?:
../../../../libsanitizer/asan/asan_linux.cc:222:20: error: ?SIGSEGV? was not declared in this scope

   return signum == SIGSEGV && common_flags()->handle_segv;
                    ^

make[6]: *** [asan_linux.lo] Error 1
make[5]: *** [all-recursive] Error 1
make[4]: *** [all] Error 2
make[3]: *** [all-target-libsanitizer] Error 2
make[2]: *** [all] Error 2
make[1]: *** [/accts/mlweber1/target/build/host-gcc-final-5.4.0/.stamp_built] Error 2
make: *** [_all] Error 2

Config to reproduce:
BR2_powerpc=y
BR2_powerpc_e500mc=y
BR2_TOOLCHAIN_BUILDROOT_GLIBC=y
BR2_KERNEL_HEADERS_VERSION=y
BR2_DEFAULT_KERNEL_VERSION="3.12.37"
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_3_12=y
BR2_GCC_VERSION_5_X=y
BR2_TOOLCHAIN_BUILDROOT_CXX=y
BR2_GCC_ENABLE_LTO=y

The resolution looks to be
https://www.mail-archive.com/gcc-patches at gcc.gnu.org/msg159613.html

I'll get a patch tested and I can confirm so far that the issue goes away in GCC6 but GCC5.4 has the bug.

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=10061

--- Comment #1 from Matt Weber <[email protected]> --- Confirmed, that patch does resolve the issue.

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=10061

Thomas Petazzoni <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #2 from Thomas Petazzoni <[email protected]> --- Fixed by your own patch, applied as of commit
https://git.buildroot.org/buildroot/commit/?id=5c90f6a7b68ebdc43ea72b763ec98a0a300c57a1.

You are receiving this mail because:
You are on the CC list for the bug.