public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "StevenSun2021 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/101681] PMF comparison to nullptr is not considered a constexpr Date: Fri, 06 Aug 2021 19:08:43 +0000 [thread overview] Message-ID: <bug-101681-4-CbzZtpDsFO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101681-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101681 Steven Sun <StevenSun2021 at hotmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |StevenSun2021 at hotmail dot com --- Comment #1 from Steven Sun <StevenSun2021 at hotmail dot com> --- The following program compiles. https://godbolt.org/z/aTvchYxYW ``` struct C { void f() {} static_assert(__builtin_constant_p(&C::f)); static_assert(!__builtin_constant_p(&C::f == nullptr)); // not nonzero yet }; static_assert(__builtin_constant_p(&C::f == nullptr)); // nonzero now struct D { void f() {} static_assert(__builtin_constant_p(&C::f == nullptr)); static_assert(!__builtin_constant_p(&D::f == nullptr)); }; static_assert(__builtin_constant_p(&C::f == nullptr)); static_assert(__builtin_constant_p(&D::f == nullptr)); ``` Looks that the `&C::f` is known to be constexpr right after the function was parsed. But only when the class completely parsed, its value was assigned. We can then compare it to nullptr. To make code in comment0 accepted, we need some kind of `not null' mark on the expression tree. 0ne possible way is to assign the `&C::f` in advance, right after it was parsed.
next prev parent reply other threads:[~2021-08-06 19:08 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-29 21:05 [Bug c++/101681] New: " pinskia at gcc dot gnu.org 2021-08-06 19:08 ` StevenSun2021 at hotmail dot com [this message] 2021-08-07 0:33 ` [Bug c++/101681] " StevenSun2021 at hotmail dot com 2021-08-07 0:43 ` StevenSun2021 at hotmail dot com 2022-01-11 18:40 ` [Bug c++/101681] PMF comparison to nullptr is not considered a constexpr inside a template argument 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-101681-4-CbzZtpDsFO@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: linkBe 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).