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++/110064] New: spurious missing initializer for member for anonymous Date: Wed, 31 May 2023 15:43:24 +0000 [thread overview] Message-ID: <bug-110064-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110064 Bug ID: 110064 Summary: spurious missing initializer for member for anonymous Product: gcc Version: 13.1.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: --- This program (reduced from StackOverflow: https://stackoverflow.com/q/76375145/2069064): struct B { }; struct D : B { int x; int y; }; int main(int, char**) { D d = {.x=1, .y=2}; (void)d; } with -Wall -Wextra gives a warning on: <source>:8:22: warning: missing initializer for member 'D::<anonymous>' [-Wmissing-field-initializers] 8 | D d = {.x=1, .y=2}; | But there's... no member here that isn't initialized.
next reply other threads:[~2023-05-31 15:43 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-31 15:43 barry.revzin at gmail dot com [this message] 2023-06-02 7:36 ` [Bug c++/110064] " rguenth at gcc dot gnu.org 2023-06-05 20:34 ` mpolacek at gcc dot gnu.org 2023-07-19 20:31 ` cvs-commit at gcc dot gnu.org 2023-07-19 20:32 ` 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-110064-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).