aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/ExecutionEngine/SectionMemoryManager.cpp
diff options
context:
space:
mode:
authorLeonard Chan <leonardchan@google.com>2021-09-16 17:13:04 -0700
committerLeonard Chan <leonardchan@google.com>2021-09-16 17:14:14 -0700
commitf4092c769031f4dde5844ce57f1d47a7e7080311 (patch)
tree308c2827118a309492d3c613fb563975d6b7d28b /llvm/lib/ExecutionEngine/SectionMemoryManager.cpp
parent1d08a19a38a588a1ba39d1e0776ea331a451debd (diff)
downloadllvm-f4092c769031f4dde5844ce57f1d47a7e7080311.zip
llvm-f4092c769031f4dde5844ce57f1d47a7e7080311.tar.gz
llvm-f4092c769031f4dde5844ce57f1d47a7e7080311.tar.bz2
[compiler-rt][test] Ensure CMAKE_SYSROOT is added as a test cflag if provided
When running tests like SanitizerCommon-asan-x86_64-Linux :: Linux/crypt_r.cpp, it may attempt to use the host header crypt.h rather than a sysroot header. This is significant in the event where struct crypt_data defined on host is different from the sysroot used to make the sanitizer runtime libraries. This can result in logical differences between the expected size/layout of struct crypt_data known by sanitizers and the strict crypt_data provided by the host crypt.h. Since tests should still use the CMAKE_SYSROOT, this ensures that CMAKE_SYSROOT is propagated to compiler-rt tests. Differential Revision: https://reviews.llvm.org/D109796
Diffstat (limited to 'llvm/lib/ExecutionEngine/SectionMemoryManager.cpp')
0 files changed, 0 insertions, 0 deletions