[ubsan] Stop thinking we can rely on C++ ABI knowledge on Windows

We already disabled various tests relying on C++ ABI knowledge, but we
still tried to build in this configuration on Windows which was a
mistake.

Fixes PR26415.

llvm-svn: 259388
This commit is contained in:
Reid Kleckner 2016-02-01 19:13:28 +00:00
parent 92431703d7
commit b3e847ebac
2 changed files with 2 additions and 5 deletions

View File

@ -293,6 +293,8 @@ if(APPLE AND SANITIZER_MIN_OSX_VERSION VERSION_LESS "10.9")
# Mac OS X prior to 10.9 had problems with exporting symbols from
# libc++/libc++abi.
set(SANITIZER_CAN_USE_CXXABI FALSE)
elseif(MSVC)
set(SANITIZER_CAN_USE_CXXABI FALSE)
else()
set(SANITIZER_CAN_USE_CXXABI TRUE)
endif()

View File

@ -69,11 +69,6 @@ config.suffixes = ['.c', '.cc', '.cpp']
if config.host_os not in ['Linux', 'Darwin', 'FreeBSD', 'Windows']:
config.unsupported = True
if config.host_os == 'Windows':
# We do not currently support enough of the Microsoft ABI for UBSan to work on
# Windows.
config.available_features.remove('cxxabi')
# Allow tests to use REQUIRES=stable-runtime. For use when you cannot use XFAIL
# because the test hangs or fails on one configuration and not the other.
if config.target_arch.startswith('arm') == False and config.target_arch != 'aarch64':