[C++ Patch/RFC] PR 53025

[Paolo Carlini <paolo dot carlini at oracle dot com>]

Hi,

in this issue Daniel argued that the value of a noexcept expression 
should not depend on constructor elision. Then, in the audit trail Marc 
tentatively suggested something like the parser.c hunk below, which just 
disables our -felide-constructors optimization when parsing the noexcept 
expression. Over the last couple of days, I had a look, noticed that in 
any case we still have to handle templates, thus the pt.c hunk, and also 
that maybe we can avoid completely disabling -felide-constructors in 
noexcept expressions when we know for sure that the constructor at issue 
doen't throw: for that in call.s I'm further abusing the 
flag_elide_constructors global, in terms of using a special value of 2 
when flag_elide_constructor is found == 1 when handling the expression. 
The below passes testing, anyway.

Thanks!
Paolo.

///////////////////////

Attachment: patch_53025
Description: Text document