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++/91483] Poor diagnostic on trying to take constexpr reference to non-static object
Date: Tue, 05 Sep 2023 18:30:10 +0000	[thread overview]
Message-ID: <bug-91483-4-FCgzxM5nA6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-91483-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from CVS 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:b78cedc6b5bc062717a3e0efb10da8e19af1c422

commit r14-3718-gb78cedc6b5bc062717a3e0efb10da8e19af1c422
Author: Marek Polacek <polacek@redhat.com>
Date:   Fri Sep 1 17:26:01 2023 -0400

    c++: improve verify_constant diagnostic [PR91483]

    When verify_constant complains, it's pretty terse.  Consider

      void test ()
      {
        constexpr int i = 42;
        constexpr const int *p = &i;
      }

    where it says "'& i' is not a constant expression".  OK, but why?

    With this patch, we say:

    b.C:5:28: error: '& i' is not a constant expression
        5 |   constexpr const int *p = &i;
          |                            ^~
    b.C:5:28: note: pointer to 'i' is not a constant expression
    b.C:4:17: note: address of non-static constexpr variable 'i' may differ on
each invocation of the enclosing function; add 'static' to give it a constant
address
        4 |   constexpr int i = 42;
          |                 ^
          |                 static

    which brings g++ on par with clang++.

            PR c++/91483

    gcc/cp/ChangeLog:

            * constexpr.cc (verify_constant_explain_r): New.
            (verify_constant): Call it.

    gcc/testsuite/ChangeLog:

            * g++.dg/diagnostic/constexpr3.C: New test.

  parent reply	other threads:[~2023-09-05 18:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-91483-4@http.gcc.gnu.org/bugzilla/>
2020-09-08 15:41 ` mpolacek at gcc dot gnu.org
2023-08-25 20:26 ` mpolacek at gcc dot gnu.org
2023-09-05 18:30 ` cvs-commit at gcc dot gnu.org [this message]
2023-09-05 18:32 ` 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-91483-4-FCgzxM5nA6@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).