Re: [C++ PATCH] P0784R7 constexpr new fixes (PR c++/91369)

2019-10-31 Thread Jonathan Wakely
On 30/10/19 23:05 +0100, Jakub Jelinek wrote: On Wed, Oct 30, 2019 at 04:26:17PM -0400, Jason Merrill wrote: OK. Thanks, committed. > Now, for the accepts invalid issues. > From what I understood, in constant evaluation > ::operator new{,[]} or ::operator delete{,[]} > can't be called from

Re: [C++ PATCH] P0784R7 constexpr new fixes (PR c++/91369)

2019-10-30 Thread Jakub Jelinek
On Wed, Oct 30, 2019 at 04:26:17PM -0400, Jason Merrill wrote: > OK. > Thanks, committed. > > Now, for the accepts invalid issues. > > From what I

Re: [C++ PATCH] P0784R7 constexpr new fixes (PR c++/91369)

2019-10-30 Thread Jason Merrill
On 10/24/19 5:11 AM, Jakub Jelinek wrote: Hi! Jonathan has showed me a testcase with std::allocator::{,de}allocate and std::construct_at which FAILs with the current constexpr new implementation. There are two problems that make the testcase rejected, and further issues (not addressed by this

[C++ PATCH] P0784R7 constexpr new fixes (PR c++/91369)

2019-10-24 Thread Jakub Jelinek
Hi! Jonathan has showed me a testcase with std::allocator::{,de}allocate and std::construct_at which FAILs with the current constexpr new implementation. There are two problems that make the testcase rejected, and further issues (not addressed by this patch) where supposedly invalid C++20 code