darlinghq/darling-libcxx
1
0
Fork 0
mirror of https://github.com/darlinghq/darling-libcxx.git synced 2025-03-03 09:17:09 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

[libcxx] Add XFAILs for aligned allocation tests on AppleClang 9

Browse Source 
Some people are still running the test suite using AppleClang 9.

git-svn-id: https://llvm.org/svn/llvm-project/libcxx/trunk@348507 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Louis Dionne 2018-12-06 18:06:47 +00:00
parent edfdc498b8
commit 7ea279fbed
8 changed files with 96 additions and 96 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
test/std/language.support/support.dynamic/new.delete/new.delete.array/delete_align_val_t_replace.pass.cpp
View File

@ -20,22 +20,22 @@
// Aligned allocation was not provided before macosx10.12 and as a result we
// get availability errors when the deployment target is older than macosx10.13.
// However, AppleClang 10 (and older) don't trigger availability errors.
// XFAIL: !apple-clang-10 && availability=macosx10.12
// XFAIL: !apple-clang-10 && availability=macosx10.11
// XFAIL: !apple-clang-10 && availability=macosx10.10
// XFAIL: !apple-clang-10 && availability=macosx10.9
// XFAIL: !apple-clang-10 && availability=macosx10.8
// XFAIL: !apple-clang-10 && availability=macosx10.7
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.12
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.11
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.10
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.9
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.8
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.7
// On AppleClang 10 (and older), instead of getting an availability failure
// like above, we get a link error when we link against a dylib that does
// not export the aligned allocation functions.
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.12
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.11
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.10
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.9
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.8
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.7
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.12
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.11
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.10
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.9
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.8
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.7
// On Windows libc++ doesn't provide its own definitions for new/delete
// but instead depends on the ones in VCRuntime. However VCRuntime does not

24
test/std/language.support/support.dynamic/new.delete/new.delete.array/new_align_val_t.pass.cpp
View File

@ -18,22 +18,22 @@
// Aligned allocation was not provided before macosx10.12 and as a result we
// get availability errors when the deployment target is older than macosx10.13.
// However, AppleClang 10 (and older) don't trigger availability errors.
// XFAIL: !apple-clang-10 && availability=macosx10.12
// XFAIL: !apple-clang-10 && availability=macosx10.11
// XFAIL: !apple-clang-10 && availability=macosx10.10
// XFAIL: !apple-clang-10 && availability=macosx10.9
// XFAIL: !apple-clang-10 && availability=macosx10.8
// XFAIL: !apple-clang-10 && availability=macosx10.7
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.12
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.11
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.10
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.9
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.8
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.7
// On AppleClang 10 (and older), instead of getting an availability failure
// like above, we get a link error when we link against a dylib that does
// not export the aligned allocation functions.
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.12
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.11
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.10
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.9
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.8
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.7
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.12
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.11
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.10
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.9
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.8
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.7
// On Windows libc++ doesn't provide its own definitions for new/delete
// but instead depends on the ones in VCRuntime. However VCRuntime does not

24
test/std/language.support/support.dynamic/new.delete/new.delete.array/new_align_val_t_nothrow.pass.cpp
View File

@ -18,22 +18,22 @@
// Aligned allocation was not provided before macosx10.12 and as a result we
// get availability errors when the deployment target is older than macosx10.13.
// However, AppleClang 10 (and older) don't trigger availability errors.
// XFAIL: !apple-clang-10 && availability=macosx10.12
// XFAIL: !apple-clang-10 && availability=macosx10.11
// XFAIL: !apple-clang-10 && availability=macosx10.10
// XFAIL: !apple-clang-10 && availability=macosx10.9
// XFAIL: !apple-clang-10 && availability=macosx10.8
// XFAIL: !apple-clang-10 && availability=macosx10.7
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.12
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.11
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.10
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.9
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.8
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.7
// On AppleClang 10 (and older), instead of getting an availability failure
// like above, we get a link error when we link against a dylib that does
// not export the aligned allocation functions.
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.12
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.11
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.10
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.9
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.8
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.7
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.12
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.11
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.10
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.9
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.8
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.7
// On Windows libc++ doesn't provide its own definitions for new/delete
// but instead depends on the ones in VCRuntime. However VCRuntime does not

24
test/std/language.support/support.dynamic/new.delete/new.delete.array/new_align_val_t_nothrow_replace.pass.cpp
View File

@ -13,22 +13,22 @@
// Aligned allocation was not provided before macosx10.12 and as a result we
// get availability errors when the deployment target is older than macosx10.13.
// However, AppleClang 10 (and older) don't trigger availability errors.
// XFAIL: !apple-clang-10 && availability=macosx10.12
// XFAIL: !apple-clang-10 && availability=macosx10.11
// XFAIL: !apple-clang-10 && availability=macosx10.10
// XFAIL: !apple-clang-10 && availability=macosx10.9
// XFAIL: !apple-clang-10 && availability=macosx10.8
// XFAIL: !apple-clang-10 && availability=macosx10.7
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.12
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.11
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.10
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.9
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.8
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.7
// On AppleClang 10 (and older), instead of getting an availability failure
// like above, we get a link error when we link against a dylib that does
// not export the aligned allocation functions.
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.12
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.11
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.10
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.9
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.8
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.7
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.12
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.11
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.10
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.9
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.8
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.7
// XFAIL: no-aligned-allocation && !gcc

24
test/std/language.support/support.dynamic/new.delete/new.delete.single/delete_align_val_t_replace.pass.cpp
View File

@ -19,22 +19,22 @@
// Aligned allocation was not provided before macosx10.12 and as a result we
// get availability errors when the deployment target is older than macosx10.13.
// However, AppleClang 10 (and older) don't trigger availability errors.
// XFAIL: !apple-clang-10 && availability=macosx10.12
// XFAIL: !apple-clang-10 && availability=macosx10.11
// XFAIL: !apple-clang-10 && availability=macosx10.10
// XFAIL: !apple-clang-10 && availability=macosx10.9
// XFAIL: !apple-clang-10 && availability=macosx10.8
// XFAIL: !apple-clang-10 && availability=macosx10.7
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.12
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.11
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.10
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.9
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.8
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.7
// On AppleClang 10 (and older), instead of getting an availability failure
// like above, we get a link error when we link against a dylib that does
// not export the aligned allocation functions.
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.12
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.11
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.10
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.9
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.8
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.7
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.12
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.11
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.10
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.9
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.8
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.7
// On Windows libc++ doesn't provide its own definitions for new/delete
// but instead depends on the ones in VCRuntime. However VCRuntime does not

24
test/std/language.support/support.dynamic/new.delete/new.delete.single/new_align_val_t.pass.cpp
View File

@ -12,22 +12,22 @@
// Aligned allocation was not provided before macosx10.12 and as a result we
// get availability errors when the deployment target is older than macosx10.13.
// However, AppleClang 10 (and older) don't trigger availability errors.
// XFAIL: !apple-clang-10 && availability=macosx10.12
// XFAIL: !apple-clang-10 && availability=macosx10.11
// XFAIL: !apple-clang-10 && availability=macosx10.10
// XFAIL: !apple-clang-10 && availability=macosx10.9
// XFAIL: !apple-clang-10 && availability=macosx10.8
// XFAIL: !apple-clang-10 && availability=macosx10.7
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.12
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.11
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.10
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.9
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.8
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.7
// On AppleClang 10 (and older), instead of getting an availability failure
// like above, we get a link error when we link against a dylib that does
// not export the aligned allocation functions.
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.12
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.11
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.10
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.9
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.8
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.7
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.12
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.11
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.10
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.9
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.8
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.7
// asan and msan will not call the new handler.
// UNSUPPORTED: sanitizer-new-delete

24
test/std/language.support/support.dynamic/new.delete/new.delete.single/new_align_val_t_nothrow.pass.cpp
View File

@ -12,22 +12,22 @@
// Aligned allocation was not provided before macosx10.12 and as a result we
// get availability errors when the deployment target is older than macosx10.13.
// However, AppleClang 10 (and older) don't trigger availability errors.
// XFAIL: !apple-clang-10 && availability=macosx10.12
// XFAIL: !apple-clang-10 && availability=macosx10.11
// XFAIL: !apple-clang-10 && availability=macosx10.10
// XFAIL: !apple-clang-10 && availability=macosx10.9
// XFAIL: !apple-clang-10 && availability=macosx10.8
// XFAIL: !apple-clang-10 && availability=macosx10.7
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.12
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.11
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.10
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.9
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.8
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.7
// On AppleClang 10 (and older), instead of getting an availability failure
// like above, we get a link error when we link against a dylib that does
// not export the aligned allocation functions.
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.12
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.11
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.10
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.9
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.8
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.7
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.12
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.11
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.10
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.9
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.8
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.7
// asan and msan will not call the new handler.
// UNSUPPORTED: sanitizer-new-delete

24
test/std/language.support/support.dynamic/new.delete/new.delete.single/new_align_val_t_nothrow_replace.pass.cpp
View File

@ -13,22 +13,22 @@
// Aligned allocation was not provided before macosx10.12 and as a result we
// get availability errors when the deployment target is older than macosx10.13.
// However, AppleClang 10 (and older) don't trigger availability errors.
// XFAIL: !apple-clang-10 && availability=macosx10.12
// XFAIL: !apple-clang-10 && availability=macosx10.11
// XFAIL: !apple-clang-10 && availability=macosx10.10
// XFAIL: !apple-clang-10 && availability=macosx10.9
// XFAIL: !apple-clang-10 && availability=macosx10.8
// XFAIL: !apple-clang-10 && availability=macosx10.7
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.12
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.11
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.10
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.9
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.8
// XFAIL: !(apple-clang-9 || apple-clang-10) && availability=macosx10.7
// On AppleClang 10 (and older), instead of getting an availability failure
// like above, we get a link error when we link against a dylib that does
// not export the aligned allocation functions.
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.12
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.11
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.10
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.9
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.8
// XFAIL: apple-clang-10 && with_system_cxx_lib=macosx10.7
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.12
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.11
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.10
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.9
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.8
// XFAIL: (apple-clang-9 || apple-clang-10) && with_system_cxx_lib=macosx10.7
// NOTE: gcc doesn't provide -faligned-allocation flag to test for
// XFAIL: no-aligned-allocation && !gcc