The unavailability of posix_memalign on z/OS forces us to define _LIBCPP_HAS_NO_LIBRARY_ALIGNED_ALLOCATION'. The use of posix_memalign is being used in libcxx/src/new.cpp.
Reviewed By: #libc, ldionne
Differential Revision: https://reviews.llvm.org/D90178
# When building the dylib, don't warn for unavailable aligned allocation
# functions based on the deployment target -- they are always available
- # because they are provided by the dylib itself.
- target_add_compile_flags_if_supported(${target} PRIVATE -faligned-allocation)
+ # because they are provided by the dylib itself with the excepton of z/OS.
+ if (ZOS)
+ target_add_compile_flags_if_supported(${target} PRIVATE -fno-aligned-allocation)
+ else()
+ target_add_compile_flags_if_supported(${target} PRIVATE -faligned-allocation)
+ endif()
# On all systems the system c++ standard library headers need to be excluded.
# MSVC only has -X, which disables all default includes; including the crt.
// We're deferring to Microsoft's STL to provide aligned new et al. We don't
// have it unless the language feature test macro is defined.
# define _LIBCPP_HAS_NO_LIBRARY_ALIGNED_ALLOCATION
+#elif defined(__MVS__)
+# define _LIBCPP_HAS_NO_LIBRARY_ALIGNED_ALLOCATION
#endif
#if defined(__APPLE__)