forked from OSchip/llvm-project
c74123bdff
Disable the code appending -msse4.2 flag implicitly when the compiler supports it. The compiler support for this flags do not indicate that the underlying CPU will support SSE4.2, and passing it may result in SSE4.2 code being emitted *implicitly*. If the target platform supports SSE4.2 appropriately, the relevant bits should be already enabled via -march= or equivalent. In this case passing -msse4.2 is redundant. If a runtime detection is desired (which seems to be a case with SCUDO), then (as gcc manpage points out) the specific SSE4.2 needs to be isolated into a separate file, the -msse4.2 flag can be forced only for that file and the function defined in that file can only be called when the CPU is determined to support SSE4.2. This fixes SIGILL on SCUDO when it is compiled using gcc-5.4. Differential Revision: https://reviews.llvm.org/D28304 llvm-svn: 291217 |
||
|---|---|---|
| .. | ||
| CMakeLists.txt | ||
| scudo_allocator.cpp | ||
| scudo_allocator.h | ||
| scudo_allocator_secondary.h | ||
| scudo_flags.cpp | ||
| scudo_flags.h | ||
| scudo_flags.inc | ||
| scudo_interceptors.cpp | ||
| scudo_new_delete.cpp | ||
| scudo_termination.cpp | ||
| scudo_utils.cpp | ||
| scudo_utils.h | ||