diff options
| author | Ulrich Weigand <ulrich.weigand@de.ibm.com> | 2019-06-18 13:26:27 +0000 |
|---|---|---|
| committer | Ulrich Weigand <ulrich.weigand@de.ibm.com> | 2019-06-18 13:26:27 +0000 |
| commit | 45b10d2da5c92aa792acd282ba85c7c4f6e97f2f (patch) | |
| tree | 9551714e8cda22c6189627aa2a712cc21a3cc30b /lldb/packages/Python/lldbsuite/test/python_api/thread | |
| parent | 8d35dcd70395deb0ffebca35afffd0ad076e27ca (diff) | |
| download | bcm5719-llvm-45b10d2da5c92aa792acd282ba85c7c4f6e97f2f.tar.gz bcm5719-llvm-45b10d2da5c92aa792acd282ba85c7c4f6e97f2f.zip | |
[compiler-rt][SystemZ] Work around ASAN failures via -fno-partial-inlining
Since updating the SystemZ LLVM build bot system to Ubuntu 18.04, all bots
are red due to two ASAN failures. It turns out these are triggered due to
building the ASAN support libraries, in particular the interceptor routines
using GCC 7. Specifically, at least on our platform, this compiler decides
to "partially inline" some of those interceptors, creating intermediate
stub routines like "__interceptor_recvfrom.part.321". These will show up
in the backtraces at interception points, causing testsuite failures.
As a workaround to get the build bots green again, this patch adds the
-fno-partial-inlining command line option when building the common
sanitizer support libraries on s390x, if that option is supported by
the compiler.
llvm-svn: 363679
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/thread')
0 files changed, 0 insertions, 0 deletions
