public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fchelnokov at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/102175] New: Error comparing the pointers on static class fields in static_assert Date: Thu, 02 Sep 2021 11:14:40 +0000 [thread overview] Message-ID: <bug-102175-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102175 Bug ID: 102175 Summary: Error comparing the pointers on static class fields in static_assert Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: fchelnokov at gmail dot com Target Milestone: --- This code: ``` template<int N> struct C { static int x; }; template<int N> int C<N>::x = 0; int main() { static_assert(&C<0>::x != &C<1>::x); } ``` produces an error in GCC: "non-constant condition for static assertion", but accepted in other compilers. Demo: https://gcc.godbolt.org/z/o6dE3GaMK A similar code without templates is accepted by GCC: ``` struct C { static int x; }; int C::x = 0; struct D { static int x; }; int D::x = 0; int main() { static_assert( &D::x != &C::x ); } ```
reply other threads:[~2021-09-02 11:14 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-102175-4@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).