Some people are still running the test suite using AppleClang 9.
llvm-svn: 348507
// 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
// 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
// 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
// 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
// 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
// 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
// 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
// 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