Still expose std::align_val_t in C++17 even if we don't have aligned new/delete.
r292564 disabled the aligned new/delete overloads on platforms without posix_memalign. Unfortunately that patch also disabled the align_val_t definition in C++17 as well. This patch causes align_val_t to be exposed in C++17 regardless of if we have the new/delete overloads. git-svn-id: https://llvm.org/svn/llvm-project/libcxx/trunk@292582 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
@@ -145,7 +145,7 @@ public:
|
|||||||
|
|
||||||
#endif // defined(_LIBCPP_BUILDING_NEW) || (_LIBCPP_STD_VER > 11)
|
#endif // defined(_LIBCPP_BUILDING_NEW) || (_LIBCPP_STD_VER > 11)
|
||||||
|
|
||||||
#ifndef _LIBCPP_HAS_NO_ALIGNED_ALLOCATION
|
#if !defined(_LIBCPP_HAS_NO_ALIGNED_ALLOCATION) || _LIBCPP_STD_VER > 14
|
||||||
#ifndef _LIBCPP_CXX03_LANG
|
#ifndef _LIBCPP_CXX03_LANG
|
||||||
enum class _LIBCPP_ENUM_VIS align_val_t : size_t { };
|
enum class _LIBCPP_ENUM_VIS align_val_t : size_t { };
|
||||||
#else
|
#else
|
||||||
|
|||||||
Reference in New Issue
Block a user