summaryrefslogtreecommitdiffstats
path: root/libcxx/include/new
diff options
context:
space:
mode:
authorEric Fiselier <eric@efcs.ca>2017-01-20 06:27:34 +0000
committerEric Fiselier <eric@efcs.ca>2017-01-20 06:27:34 +0000
commit9114f45ab87076a6998fb8a72958345cd2a94498 (patch)
tree717de872ed5379ab7e35852431830d1353d87ebf /libcxx/include/new
parent5dc021bf45ba8d20e9d0734e4b753f354bbad01c (diff)
downloadbcm5719-llvm-9114f45ab87076a6998fb8a72958345cd2a94498.tar.gz
bcm5719-llvm-9114f45ab87076a6998fb8a72958345cd2a94498.zip
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. llvm-svn: 292582
Diffstat (limited to 'libcxx/include/new')
-rw-r--r--libcxx/include/new2
1 files changed, 1 insertions, 1 deletions
diff --git a/libcxx/include/new b/libcxx/include/new
index 6e43501d299..86428f281dc 100644
--- a/libcxx/include/new
+++ b/libcxx/include/new
@@ -145,7 +145,7 @@ public:
#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
enum class _LIBCPP_ENUM_VIS align_val_t : size_t { };
#else
OpenPOWER on IntegriCloud