public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/106650] [C++23] P2280 - Using unknown references in constant expressions
Date: Wed, 29 Nov 2023 22:10:43 +0000	[thread overview]
Message-ID: <bug-106650-4-PIxKW3PAx7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106650-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Marek Polacek <mpolacek@gcc.gnu.org>:

https://gcc.gnu.org/g:99d114c15523e0bfe7a89ef1947f82eb5ff0260b

commit r14-5979-g99d114c15523e0bfe7a89ef1947f82eb5ff0260b
Author: Marek Polacek <polacek@redhat.com>
Date:   Fri Nov 17 14:48:44 2023 -0500

    c++: P2280R4, Using unknown refs in constant expr [PR106650]

    This patch is an attempt to implement (part of?) P2280, Using unknown
    pointers and references in constant expressions.  (Note that R4 seems to
    only allow References to unknown/Accesses via this, but not Pointers to
    unknown.)

    This patch works to the extent that the test case added in [expr.const]
    works as expected, as well as the test in
   
<https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2022/p2280r4.html#the-this-pointer>

    Most importantly, the proposal makes this compile:

      template <typename T, size_t N>
      constexpr auto array_size(T (&)[N]) -> size_t {
          return N;
      }

      void check(int const (&param)[3]) {
          constexpr auto s = array_size(param);
          static_assert (s == 3);
      }

    and I think it would be a pity not to have it in GCC 14.

    What still doesn't work is the test in $3.2:

      struct A2 { constexpr int f() { return 0; } };
      struct B2 : virtual A2 {};
      void f2(B2 &b) { constexpr int k = b.f(); }

    where we say
    error: '* & b' is not a constant expression

    This will be fixed in the future.

            PR c++/106650

    gcc/cp/ChangeLog:

            * constexpr.cc (cxx_eval_constant_expression) <case PARM_DECL>:
Allow
            reference to unknown/this as per P2280.
            <case VAR_DECL>: Allow reference to unknown as per P2280.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp0x/constexpr-array-ptr6.C: Remove dg-error.
            * g++.dg/cpp0x/constexpr-ref12.C: Likewise.
            * g++.dg/cpp0x/constexpr-ref2.C: Adjust dg-error.
            * g++.dg/cpp0x/noexcept34.C: Remove dg-error.
            * g++.dg/cpp1y/lambda-generic-const10.C: Likewise.
            * g++.dg/cpp0x/constexpr-ref13.C: New test.
            * g++.dg/cpp1z/constexpr-ref1.C: New test.
            * g++.dg/cpp1z/constexpr-ref2.C: New test.
            * g++.dg/cpp2a/constexpr-ref1.C: New test.

  parent reply	other threads:[~2023-11-29 22:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-16 17:08 [Bug c++/106650] New: " mpolacek at gcc dot gnu.org
2022-12-09 15:27 ` [Bug c++/106650] " pinskia at gcc dot gnu.org
2023-11-16 22:36 ` mpolacek at gcc dot gnu.org
2023-11-17 21:47 ` mpolacek at gcc dot gnu.org
2023-11-29 22:10 ` cvs-commit at gcc dot gnu.org [this message]
2023-11-29 22:24 ` mpolacek 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-106650-4-PIxKW3PAx7@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).