Re: [libcxx] r292582 - Still expose std::align_val_t in C++17 even if we don't have aligned new/delete.

2017-01-20 Thread Marshall Clow via cfe-commits
On Thu, Jan 19, 2017 at 10:40 PM, Eric Fiselier wrote: > Hi All, > > This patch addresses issues introduced by r292564. Specifically it makes > `align_val_t.pass.cpp` pass in C++17 even if the system > doesn't support aligned new/delete. > > Because r292564 was merged into 4.0,

Re: [libcxx] r292582 - Still expose std::align_val_t in C++17 even if we don't have aligned new/delete.

2017-01-20 Thread Eric Fiselier via cfe-commits
Merged as r292586. I waited for all of the failing bots to rerun, but I didn't want to break builds all night. /Eric On Thu, Jan 19, 2017 at 11:40 PM, Eric Fiselier wrote: > Hi All, > > This patch addresses issues introduced by r292564. Specifically it makes >

Re: [libcxx] r292582 - Still expose std::align_val_t in C++17 even if we don't have aligned new/delete.

2017-01-19 Thread Eric Fiselier via cfe-commits
Hi All, This patch addresses issues introduced by r292564. Specifically it makes `align_val_t.pass.cpp` pass in C++17 even if the system doesn't support aligned new/delete. Because r292564 was merged into 4.0, this should be as well. @Marshall can you OK this? /Eric On Thu, Jan 19, 2017 at

[libcxx] r292582 - Still expose std::align_val_t in C++17 even if we don't have aligned new/delete.

2017-01-19 Thread Eric Fiselier via cfe-commits
Author: ericwf Date: Fri Jan 20 00:27:34 2017 New Revision: 292582 URL: http://llvm.org/viewvc/llvm-project?rev=292582=rev Log: 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.