On Mon, Nov 13, 2017 at 6:53 AM, Ville Voutilainen
wrote:
> * g++.dg/tree-ssa/pr31146-2.C: Likewise.
> * g++.dg/tree-ssa/pr31146-3.C: New.
> * g++.dg/tree-ssa/pr41428-2.C: Likewise.
> * g++.dg/tree-ssa/pr41428.C: Adjust.
These are testing optimizations, so let's just add -fcheck-n
On 13 November 2017 at 14:17, Eric Botcazou wrote:
>> 2017-11-13 Ville Voutilainen
>>
>> gcc/
>>
>> Remove the null check from placement new in all modes
>> * cp/init.c (build_new_1): Don't do a null check for
>> a namespace-scope non-replaceable placement new
>> in any mode
> 2017-11-13 Ville Voutilainen
>
> gcc/
>
> Remove the null check from placement new in all modes
> * cp/init.c (build_new_1): Don't do a null check for
> a namespace-scope non-replaceable placement new
> in any mode unless -fcheck-new is provided.
Incorrect entry, it shou
On 10 November 2017 at 18:55, Ville Voutilainen
wrote:
> On 10 November 2017 at 18:19, Jason Merrill wrote:
>> OK.
>
>
> I see non-obvious testsuite failures, I'll see if adding -fcheck-new
> to those cases
> cures the problem. Please stay tuned. :)
Here. Tested on Linux-PPC64 and Linux-x64.
20
On 10 November 2017 at 18:19, Jason Merrill wrote:
> OK.
I see non-obvious testsuite failures, I'll see if adding -fcheck-new
to those cases
cures the problem. Please stay tuned. :)
OK.
On Fri, Nov 10, 2017 at 12:29 AM, Ville Voutilainen
wrote:
> Tested manually on Linux-X64, finishing testing with the full suite on
> Linux-PPC64.
>
> I spent far too much time contemplating whether to add a compatibility switch
> for this, but -fcheck-new *is* such a compatibility switch.
>
