6805c1c6a6
The latest Solaris 11.4/x86 update uncovered a libsanitizer bug that caused one test to FAIL for 32-bit: +FAIL: c-c++-common/asan/null-deref-1.c -O0 output pattern test +FAIL: c-c++-common/asan/null-deref-1.c -O1 output pattern test +FAIL: c-c++-common/asan/null-deref-1.c -O2 output pattern test +FAIL: c-c++-common/asan/null-deref-1.c -O2 -flto output pattern test +FAIL: c-c++-common/asan/null-deref-1.c -O2 -flto -flto-partition=none output pattern test +FAIL: c-c++-common/asan/null-deref-1.c -O3 -g output pattern test +FAIL: c-c++-common/asan/null-deref-1.c -Os output pattern test I've identified the problem and the fix has just landed in upstream llvm-project: https://reviews.llvm.org/D83664 Tested on i386-pc-solaris2.11 and x86_64-pc-linux.gnu. libsanitizer: * sanitizer_common/sanitizer_linux.cpp: Cherry-pick llvm-project revision f0e9b76c3500496f8f3ea7abe6f4bf801e3b41e7. |
||
|---|---|---|
| .. | ||
| asan | ||
| builtins | ||
| include | ||
| interception | ||
| libbacktrace | ||
| lsan | ||
| sanitizer_common | ||
| tsan | ||
| ubsan | ||
| acinclude.m4 | ||
| aclocal.m4 | ||
| ChangeLog | ||
| config.h.in | ||
| configure | ||
| configure.ac | ||
| configure.tgt | ||
| HOWTO_MERGE | ||
| libsanitizer.spec.in | ||
| LICENSE.TXT | ||
| LOCAL_PATCHES | ||
| Makefile.am | ||
| Makefile.in | ||
| MERGE | ||
| merge.sh | ||
| README.gcc | ||
AddressSanitizer and ThreadSanitizer (https://github.com/google/sanitizers) are projects initially developed by Google Inc. Both tools consist of a compiler module and a run-time library. The sources of the run-time library for these projects are hosted at https://github.com/llvm/llvm-project in the following directories: compiler-rt/include/sanitizer compiler-rt/lib/sanitizer_common compiler-rt/lib/interception compiler-rt/lib/asan compiler-rt/lib/tsan compiler-rt/lib/lsan compiler-rt/lib/ubsan Trivial and urgent fixes (portability, build fixes, etc.) may go directly to the GCC tree. All non-trivial changes, functionality improvements, etc. should go through the upstream tree first and then be merged back to the GCC tree. The merges from upstream should be done with the aid of the merge.sh script; it will also update the file MERGE to contain the upstream revision we merged with.