public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "barry.revzin at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/71962] error: ‘((& x) != 0u)’ is not a constant expression Date: Mon, 25 Mar 2024 15:40:35 +0000 [thread overview] Message-ID: <bug-71962-4-fQyo8ncy0m@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-71962-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71962 Barry Revzin <barry.revzin at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |barry.revzin at gmail dot com --- Comment #12 from Barry Revzin <barry.revzin at gmail dot com> --- Similar failure: struct A { void f(); }; int main() { constexpr auto pmf = &A::f; static_assert(pmf != nullptr); // error with UBSAN only } This surfaces from attempting to implement function_ref (https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2023/p0792r14.html) which has a constructor that takes the callable as a non-type template parameter and static_asserts that it's not a null pointer. Which apparently doesn't work with UBSAN.
prev parent reply other threads:[~2024-03-25 15:40 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-71962-4@http.gcc.gnu.org/bugzilla/> 2020-03-30 21:54 ` herring at lanl dot gov 2022-12-31 21:44 ` pinskia at gcc dot gnu.org 2023-06-30 4:32 ` pinskia at gcc dot gnu.org 2024-03-25 15:40 ` barry.revzin at gmail dot com [this message]
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-71962-4-fQyo8ncy0m@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).