[PATCH] c++, v2: Implement C++29 P3950R1 - return_value & return_void Are Not Mutually Exclusive paper as DR [PR125830]
Jason Merrill
jason@redhat.com
Sat Oct 3 07:24:20 GMT 2026
On 10/3/26 7:25 AM, Jakub Jelinek wrote:
> On Fri, Oct 02, 2026 at 11:20:45PM +0200, Jason Merrill wrote:
>> Everything in that function should change tf_warning_or_error to complain.
>
> Ok, here is an updated patch which adds it to the remaining call -
> build_op_call.
OK, thanks.
>>> So far lightly tested (on coroutines/* and affected tests), ok for trunk
>>> if it passes full bootstrap/regtest? And what to do about the above
>>> mentioned bugs in the code being removed? Shall I address those first
>>> and then send this patch to remove it afterwards (and just backport that
>>> first patch and not the second)?
>>
>> Do you think it's important to fix those bugs on release branches? They
>> sound like minor diagnostic quality issues.
>
> It is an ICE after error, e.g. g++ 15.2.1 emits on:
Yeah, ice-after-error fixes don't seem important to backport.
Jason
More information about the Gcc-patches
mailing list