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 c++/96557] New: Diagnostics: Can you tell me why it's not a constant expression? Date: Mon, 10 Aug 2020 16:25:30 +0000 [thread overview] Message-ID: <bug-96557-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96557 Bug ID: 96557 Summary: Diagnostics: Can you tell me why it's not a constant expression? Product: gcc Version: 10.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: barry.revzin at gmail dot com Target Milestone: --- Consider: struct X { char storage[100] = {}; char const* head = storage; }; void f() { constexpr X x = {}; } gcc correctly rejects this with: error: 'X{"", ((const char*)(& x.X::storage))}' is not a constant expression 7 | constexpr X x = {}; | ^ It'd be great if the error here actually indicated _why_ it's not a constant expression (or how to fix it). clang does a little bit better: <source>:7:17: error: constexpr variable 'x' must be initialized by a constant expression constexpr X x = {}; ^ ~~ <source>:7:17: note: pointer to subobject of 'x' is not a constant expression <source>:7:17: note: declared here But ideally we get some message about specifically 'head' pointing to 'storage' and a fixup suggesting making the variable x static.
next reply other threads:[~2020-08-10 16:25 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-10 16:25 barry.revzin at gmail dot com [this message] 2020-08-10 16:40 ` [Bug c++/96557] " 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-96557-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).