public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/110064] spurious missing initializer for member for anonymous Date: Wed, 19 Jul 2023 20:31:59 +0000 [thread overview] Message-ID: <bug-110064-4-Ncsv9N2Th9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110064-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110064 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Marek Polacek <mpolacek@gcc.gnu.org>: https://gcc.gnu.org/g:b1ae46bdd19fc2aaea41bc894168bdaf4799be80 commit r14-2657-gb1ae46bdd19fc2aaea41bc894168bdaf4799be80 Author: Marek Polacek <polacek@redhat.com> Date: Wed Jul 19 13:31:52 2023 -0400 c++: -Wmissing-field-initializers and empty class [PR110064] Let's suppress -Wmissing-field-initializers for empty classes. Here I don't think I need the usual COMPLETE_TYPE_P/dependent_type_p checks. PR c++/110064 gcc/cp/ChangeLog: * typeck2.cc (process_init_constructor_record): Don't emit -Wmissing-field-initializers for empty classes. gcc/testsuite/ChangeLog: * g++.dg/warn/Wmissing-field-initializers-3.C: New test.
next prev parent reply other threads:[~2023-07-19 20:31 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-31 15:43 [Bug c++/110064] New: " barry.revzin at gmail dot com 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 [this message] 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-Ncsv9N2Th9@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).