public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jason Merrill <jason@redhat.com>
To: Marek Polacek <polacek@redhat.com>,
	GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] c++: noexcept and copy elision [PR109030]
Date: Tue, 7 Mar 2023 09:55:04 -0500	[thread overview]
Message-ID: <1db0f19a-3394-03dd-94f4-24bf59b94881@redhat.com> (raw)
In-Reply-To: <20230306235957.390533-1-polacek@redhat.com>

On 3/6/23 18:59, Marek Polacek wrote:
> When processing a noexcept, constructors aren't elided: build_over_call
> has
> 	 /* It's unsafe to elide the constructor when handling
> 	    a noexcept-expression, it may evaluate to the wrong
> 	    value (c++/53025).  */
> 	 && (force_elide || cp_noexcept_operand == 0))
> so the assert I added recently needs to be relaxed a little bit.
> 
> Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for trunk?

OK.

> 	PR c++/109030
> 
> gcc/cp/ChangeLog:
> 
> 	* constexpr.cc (cxx_eval_call_expression): Relax assert.
> 
> gcc/testsuite/ChangeLog:
> 
> 	* g++.dg/cpp0x/noexcept77.C: New test.
> ---
>   gcc/cp/constexpr.cc                     | 6 +++++-
>   gcc/testsuite/g++.dg/cpp0x/noexcept77.C | 9 +++++++++
>   2 files changed, 14 insertions(+), 1 deletion(-)
>   create mode 100644 gcc/testsuite/g++.dg/cpp0x/noexcept77.C
> 
> diff --git a/gcc/cp/constexpr.cc b/gcc/cp/constexpr.cc
> index 364695b762c..5384d0e8e46 100644
> --- a/gcc/cp/constexpr.cc
> +++ b/gcc/cp/constexpr.cc
> @@ -2869,7 +2869,11 @@ cxx_eval_call_expression (const constexpr_ctx *ctx, tree t,
>   
>     /* We used to shortcut trivial constructor/op= here, but nowadays
>        we can only get a trivial function here with -fno-elide-constructors.  */
> -  gcc_checking_assert (!trivial_fn_p (fun) || !flag_elide_constructors);
> +  gcc_checking_assert (!trivial_fn_p (fun)
> +		       || !flag_elide_constructors
> +		       /* We don't elide constructors when processing
> +			  a noexcept-expression.  */
> +		       || cp_noexcept_operand);
>   
>     bool non_constant_args = false;
>     new_call.bindings
> diff --git a/gcc/testsuite/g++.dg/cpp0x/noexcept77.C b/gcc/testsuite/g++.dg/cpp0x/noexcept77.C
> new file mode 100644
> index 00000000000..16db8eb79ee
> --- /dev/null
> +++ b/gcc/testsuite/g++.dg/cpp0x/noexcept77.C
> @@ -0,0 +1,9 @@
> +// PR c++/109030
> +// { dg-do compile { target c++11 } }
> +
> +struct foo { };
> +
> +struct __as_receiver {
> +  foo empty_env;
> +};
> +void sched(foo __fun) noexcept(noexcept(__as_receiver{__fun})) { }
> 
> base-commit: dfb14cdd796ad9df6b5f2def047ef36b29385902


  reply	other threads:[~2023-03-07 14:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-06 23:59 Marek Polacek
2023-03-07 14:55 ` Jason Merrill [this message]
2023-03-09 19:32 ` Patrick Palka
2023-03-09 23:12   ` Jason Merrill
2023-03-15 23:47     ` Patrick Palka
2023-03-16 14:09       ` Patrick Palka
2023-03-16 14:38         ` Jason Merrill
2023-03-16 15:48           ` Patrick Palka
2023-03-16 15:59             ` Jason Merrill

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1db0f19a-3394-03dd-94f4-24bf59b94881@redhat.com \
    --to=jason@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=polacek@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).