public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/107685] [C++23] P2647 - Permitting static constexpr variables in constexpr functions
Date: Sat, 19 Nov 2022 09:21:54 +0000	[thread overview]
Message-ID: <bug-107685-4-0PbGkmP2yb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107685-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107685

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
https://gcc.gnu.org/g:32d16fe9d7e347bc58e7fad316ed7923e1d0f65c

commit r13-4161-g32d16fe9d7e347bc58e7fad316ed7923e1d0f65c
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Sat Nov 19 09:26:44 2022 +0100

    c++: Implement C++23 P2647R1 - Permitting static constexpr variables in
constexpr functions

    The following patch implements this paper.
    Per further discussions it is implemented for C++23 only, so isn't
    treated as a DR, e.g. because the part of the standard the paper is
    changing didn't even exist in C++20.
    And we gave up on trying to implement it as a pedwarn rather than
    error for C++20 and older, because of implicit constexpr lambdas or
    -fimplicit-constexpr reasons.
    For C++20 and older, the only change is that passing through
    definitions of static or thread_local vars usable in constant expressions
    is now accepted in statement expressions if they aren't inside of constexpr
    or consteval functions.

    2022-11-19  Jakub Jelinek  <jakub@redhat.com>

    gcc/c-family/
            * c-cppbuiltin.cc (c_cpp_builtins): Bump __cpp_constexpr
            value from 202207L to 202211L.
    gcc/cp/
            * constexpr.cc (cxx_eval_constant_expression): Implement C++23
            P2647R1 - Permitting static constexpr variables in constexpr
functions.
            Allow DECL_EXPRs of decl_constant_var_p static or thread_local
vars.
            (potential_constant_expression_1): Similarly, except use
            decl_maybe_constant_var_p instead of decl_constant_var_p if
            processing_template_decl.
    gcc/testsuite/
            * g++.dg/cpp23/constexpr-nonlit17.C: New test.
            * g++.dg/cpp23/constexpr-nonlit18.C: New test.
            * g++.dg/cpp23/feat-cxx2b.C: Adjust expected __cpp_constexpr
            value.
            * g++.dg/ext/stmtexpr19.C: Don't expect an error.
            * g++.dg/ext/stmtexpr25.C: New test.

  parent reply	other threads:[~2022-11-19  9:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-14 18:30 [Bug c++/107685] New: " mpolacek at gcc dot gnu.org
2022-11-14 18:30 ` [Bug c++/107685] " mpolacek at gcc dot gnu.org
2022-11-19  9:21 ` jakub at gcc dot gnu.org [this message]
2022-11-28 22:31 ` pinskia at gcc dot gnu.org

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=bug-107685-4-0PbGkmP2yb@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).