public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nathanieloshead at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/113047] dereferencing a null pointer in a constant expression
Date: Tue, 19 Dec 2023 22:31:59 +0000	[thread overview]
Message-ID: <bug-113047-4-TABbf000vI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113047-4@http.gcc.gnu.org/bugzilla/>

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

Nathaniel Shead <nathanieloshead at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |nathanieloshead at gmail dot com

--- Comment #4 from Nathaniel Shead <nathanieloshead at gmail dot com> ---
I've pushed a fix for PR102420 (and hence comment #1), but looking at the DR
this isn't sufficient for the result of CWG2823, for which presumably all of
the following should also start erroring as well (note none of these error in
Clang yet either):

  struct X {
    static constexpr int f() { return 0; }
  };

  constexpr int g(X* x) { return (*x).f(); }  // error
  constexpr int a = g(nullptr);

  constexpr int h(X* x) { return x->f(); }  // error
  constexpr int b = h(nullptr);

  // and similarly
  constexpr int test() {
    int* p = nullptr;
    *p;  // error
    return 0;
  }
  constexpr int t = test();

  parent reply	other threads:[~2023-12-19 22:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-16 21:01 [Bug c++/113047] New: " gcc_bz at brnz dot org
2023-12-16 21:02 ` [Bug c++/113047] " gcc_bz at brnz dot org
2023-12-16 21:16 ` pinskia at gcc dot gnu.org
2023-12-19  4:22 ` de34 at live dot cn
2023-12-19 22:31 ` nathanieloshead at gmail dot com [this message]
2024-01-18 19:17 ` 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-113047-4-TABbf000vI@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).