maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity

[libcxx] Rejigger test for destroying delete feature-test macros 

In r361572, we introduced library support for C++20 destroying delete
and decided to only define the library feature-test macro when the
compiler supports the underlying language feature. This patch reworks
the tests to mirror that.

llvm-svn: 366263
This commit is contained in:
Louis Dionne 2019-07-16 21:13:40 +00:00
parent 588fc9e756
commit e559f62506
1 changed files with 13 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
libcxx/test/std/language.support/support.dynamic/destroying_delete_t.pass.cpp
View File

@ -52,10 +52,19 @@ void A::operator delete(A* a, std::destroying_delete_t) {
::operator delete(a);
}
#ifndef __cpp_lib_destroying_delete
#error "Expected __cpp_lib_destroying_delete to be defined"
#elif __cpp_lib_destroying_delete < 201806L
#error "Unexpected value of __cpp_lib_destroying_delete"
// Only test the definition of the library feature-test macro when the compiler
// supports the feature -- otherwise we don't define the library feature-test
// macro.
#if defined(__cpp_impl_destroying_delete)
# if !defined(__cpp_lib_destroying_delete)
# error "Expected __cpp_lib_destroying_delete to be defined"
# elif __cpp_lib_destroying_delete < 201806L
# error "Unexpected value of __cpp_lib_destroying_delete"
# endif
#else
# if defined(__cpp_lib_destroying_delete)
# error "The library feature-test macro for destroying delete shouldn't be defined when the compiler doesn't support the language feature"
# endif
#endif
int main() {