From: Marek Polacek <polacek@redhat.com>
To: Jason Merrill <jason@redhat.com>
Cc: Patrick Palka <ppalka@redhat.com>, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] c++: ICE with template NEW_EXPR [PR105803]
Date: Thu, 2 Jun 2022 16:33:54 -0400 [thread overview]
Message-ID: <Ypkesr/hNhGPvG47@redhat.com> (raw)
In-Reply-To: <f1d10f7d-149c-b437-fcac-5f284ea2df78@redhat.com>
On Thu, Jun 02, 2022 at 04:26:27PM -0400, Jason Merrill wrote:
> On 6/2/22 16:10, Marek Polacek wrote:
> > index 1346a1d4c10..2bbd8785627 100644
> > --- a/gcc/cp/constexpr.cc
> > +++ b/gcc/cp/constexpr.cc
> > @@ -9039,10 +9039,18 @@ potential_constant_expression_1 (tree t, bool want_rval, bool strict, bool now,
> > "before C++17");
> > return false;
> > - case DYNAMIC_CAST_EXPR:
> > - case PSEUDO_DTOR_EXPR:
> > case NEW_EXPR:
> > case VEC_NEW_EXPR:
> > + if (cxx_dialect >= cxx20)
> > + /* In C++20, new-expressions are potentially constant. */
> > + return true;
> > + else if (flags & tf_error)
> > + error_at (loc, "new-expression is not a constant expression "
> > + "before C++20");
> > + return false;
> > +
> > + case DYNAMIC_CAST_EXPR:
> > + case PSEUDO_DTOR_EXPR:
> > case DELETE_EXPR:
> > case VEC_DELETE_EXPR:
>
> Delete, too.
Duh. Fixed:
From 2423f6548405185e256036df3d0ef3c13fd996c5 Mon Sep 17 00:00:00 2001
From: Marek Polacek <polacek@redhat.com>
Date: Thu, 2 Jun 2022 15:56:18 -0400
Subject: [PATCH] c++: new-expression is potentially constant in C++20
... so adjust p_c_e accordingly.
gcc/cp/ChangeLog:
* constexpr.cc (potential_constant_expression_1): Treat
{,VEC_}NEW_EXPR and {,VEC_}DELETE_EXPRas potentially constant in C++20.
---
gcc/cp/constexpr.cc | 12 ++++++++++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/gcc/cp/constexpr.cc b/gcc/cp/constexpr.cc
index 1346a1d4c10..684238883dc 100644
--- a/gcc/cp/constexpr.cc
+++ b/gcc/cp/constexpr.cc
@@ -9039,12 +9039,20 @@ potential_constant_expression_1 (tree t, bool want_rval, bool strict, bool now,
"before C++17");
return false;
- case DYNAMIC_CAST_EXPR:
- case PSEUDO_DTOR_EXPR:
case NEW_EXPR:
case VEC_NEW_EXPR:
case DELETE_EXPR:
case VEC_DELETE_EXPR:
+ if (cxx_dialect >= cxx20)
+ /* In C++20, new-expressions are potentially constant. */
+ return true;
+ else if (flags & tf_error)
+ error_at (loc, "new-expression is not a constant expression "
+ "before C++20");
+ return false;
+
+ case DYNAMIC_CAST_EXPR:
+ case PSEUDO_DTOR_EXPR:
case THROW_EXPR:
case OMP_PARALLEL:
case OMP_TASK:
base-commit: 7b98910406b5000a6429c188b0c6cc14e3140637
--
2.36.1
next prev parent reply other threads:[~2022-06-02 20:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 22:45 Marek Polacek
2022-06-02 12:42 ` Patrick Palka
2022-06-02 14:03 ` Marek Polacek
2022-06-02 19:42 ` Jason Merrill
2022-06-02 20:10 ` Marek Polacek
2022-06-02 20:26 ` Jason Merrill
2022-06-02 20:33 ` Marek Polacek [this message]
2022-06-02 20:38 ` 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=Ypkesr/hNhGPvG47@redhat.com \
--to=polacek@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=ppalka@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).