From: Jakub Jelinek <jakub@redhat.com>
To: Jason Merrill <jason@redhat.com>
Cc: Jonathan Wakely <jwakely@redhat.com>,
gcc-patches@gcc.gnu.org, Marek Polacek <polacek@redhat.com>
Subject: Re: [PATCH] c++, v2: Implement C++23 P2647R1 - Permitting static constexpr variables in constexpr functions
Date: Wed, 16 Nov 2022 15:08:27 +0100 [thread overview]
Message-ID: <Y3Tu29pNW41Vzz+G@tucnak> (raw)
In-Reply-To: <dbf3df41-0e64-cbf2-025d-ab0e365cc8ba@redhat.com>
On Wed, Nov 16, 2022 at 08:20:34AM -0500, Jason Merrill wrote:
> > Ok. But there is another issue, the
> > https://eel.is/c++draft/expr.const#5.2
> > spot that P2647R1 is changing didn't exist in C++20, it was only added with
> > P2242R3. So, if one would treat P2647R1 as a DR for C++20, one has to come up with
> > a different standard modification.
> > Probably change the last bullet of:
> > [dcl.constexpr]/3
> > its function-body shall not enclose
> >
> > a goto statement,
> > an identifier label,
> > a definition of a variable of non-literal type or of static or thread storage duration.
> > to
> > a definition of a variable of non-literal type or of a non-constexpr
> > variable of static or thread storage duration.
> > or so.
>
> Indeed, though the hypothetical C++20 change could still use the "usable in
> constant expressions" phrase.
Yes.
Though, with -std=c++20 we are rejected already in start_decl's
if (current_function_decl && VAR_P (decl)
&& DECL_DECLARED_CONSTEXPR_P (current_function_decl)
&& cxx_dialect < cxx23)
{
bool ok = false;
if (CP_DECL_THREAD_LOCAL_P (decl) && !DECL_REALLY_EXTERN (decl))
error_at (DECL_SOURCE_LOCATION (decl),
"%qD defined %<thread_local%> in %qs function only "
"available with %<-std=c++2b%> or %<-std=gnu++2b%>", decl,
DECL_IMMEDIATE_FUNCTION_P (current_function_decl)
? "consteval" : "constexpr");
else if (TREE_STATIC (decl))
error_at (DECL_SOURCE_LOCATION (decl),
"%qD defined %<static%> in %qs function only available "
"with %<-std=c++2b%> or %<-std=gnu++2b%>", decl,
DECL_IMMEDIATE_FUNCTION_P (current_function_decl)
? "consteval" : "constexpr");
else
ok = true;
if (!ok)
cp_function_chain->invalid_constexpr = true;
}
and at that point I fear decl_maybe_constant_var_p will not work
properly. Shall this hunk be moved somewhere else (cp_finish_decl?)
where we can already call it, or do the above in start_decl for
cxx_dialect < cxx20 and add a cxx_dialect == cxx20 hunk in cp_finish_decl?
Jakub
next prev parent reply other threads:[~2022-11-16 14:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 17:07 [PATCH] c++: " Jakub Jelinek
2022-11-13 11:45 ` [PATCH] c++, v2: " Jakub Jelinek
2022-11-15 23:36 ` Jason Merrill
2022-11-15 23:50 ` Jakub Jelinek
2022-11-16 0:27 ` Jonathan Wakely
2022-11-16 6:19 ` Jakub Jelinek
2022-11-16 13:20 ` Jason Merrill
2022-11-16 14:08 ` Jakub Jelinek [this message]
2022-11-16 14:33 ` Jason Merrill
2022-11-16 14:46 ` Jakub Jelinek
2022-11-16 20:26 ` Jason Merrill
2022-11-17 9:13 ` [PATCH] c++, v3: " Jakub Jelinek
2022-11-17 14:42 ` Jason Merrill
2022-11-17 18:42 ` Jakub Jelinek
2022-11-17 20:42 ` [PATCH] c++, v4: " Jakub Jelinek
2022-11-18 0:15 ` Marek Polacek
2022-11-18 7:48 ` Jakub Jelinek
2022-11-18 15:03 ` Marek Polacek
2022-11-18 15:14 ` Jakub Jelinek
2022-11-18 16:24 ` Jason Merrill
2022-11-18 16:34 ` Jakub Jelinek
2022-11-18 16:52 ` Jason Merrill
2022-11-18 0:28 ` Jason Merrill
2022-11-18 9:10 ` [PATCH] c++, v5: " Jakub Jelinek
2022-11-16 0:26 ` [PATCH] c++, v2: " Jonathan Wakely
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=Y3Tu29pNW41Vzz+G@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=jwakely@redhat.com \
--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).