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/82283] Wrong warning with -Wmissing-field-initializers
Date: Tue, 29 Mar 2022 01:46:41 +0000	[thread overview]
Message-ID: <bug-82283-4-crezHNewRR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-82283-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82283

--- Comment #17 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Marek Polacek
<mpolacek@gcc.gnu.org>:

https://gcc.gnu.org/g:0fa9022aa30b9c4dde965a0406943c8c0af5eb54

commit r11-9715-g0fa9022aa30b9c4dde965a0406943c8c0af5eb54
Author: Marek Polacek <polacek@redhat.com>
Date:   Tue Mar 22 14:37:02 2022 -0400

    c: -Wmissing-field-initializers and designated inits [PR82283, PR84685]

    This patch fixes two kinds of wrong -Wmissing-field-initializers
    warnings.  Our docs say that this warning "does not warn about designated
    initializers", but we give a warning for

    1) the array case:

      struct S {
        struct N {
          int a;
          int b;
        } c[1];
      } d = {
        .c[0].a = 1,
        .c[0].b = 1, // missing initializer for field 'b' of 'struct N'
      };

    we warn because push_init_level, when constructing an array, clears
    constructor_designated (which the warning relies on), and we forget
    that we were in a designated initializer context.  Fixed by the
    push_init_level hunk; and

    2) the compound literal case:

      struct T {
        int a;
        int *b;
        int c;
      };

      struct T t = { .b = (int[]){1} }; // missing initializer for field 'c' of
'struct T'

    where set_designator properly sets constructor_designated to 1, but the
    compound literal causes us to create a whole new initializer_stack in
    start_init, which clears constructor_designated.  Then, after we've parsed
    the compound literal, finish_init flushes the initializer_stack entry,
    but doesn't restore constructor_designated, so we forget we were in
    a designated initializer context, which causes the bogus warning.  (The
    designated flag is also tracked in constructor_stack, but in this case,
    we didn't perform push_init_level between set_designator and start_init
    so it wasn't saved anywhere.)

            PR c/82283
            PR c/84685

    gcc/c/ChangeLog:

            * c-typeck.c (struct initializer_stack): Add 'designated' member.
            (start_init): Set it.
            (finish_init): Restore constructor_designated.
            (push_init_level): Set constructor_designated to the value of
            constructor_designated in the upper constructor_stack.

    gcc/testsuite/ChangeLog:

            * gcc.dg/Wmissing-field-initializers-1.c: New test.
            * gcc.dg/Wmissing-field-initializers-2.c: New test.
            * gcc.dg/Wmissing-field-initializers-3.c: New test.
            * gcc.dg/Wmissing-field-initializers-4.c: New test.
            * gcc.dg/Wmissing-field-initializers-5.c: New test.

    (cherry picked from commit 4b7d9f8f51bd96d290aac230c71e501fcb6b21a6)

  parent reply	other threads:[~2022-03-29  1:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-82283-4@http.gcc.gnu.org/bugzilla/>
2020-05-12 19:53 ` marxin at gcc dot gnu.org
2021-04-14  9:39 ` robert.dumitru at cyberthorstudios dot com
2021-04-14  9:56 ` redi at gcc dot gnu.org
2022-02-04  8:28 ` rsandifo at gcc dot gnu.org
2022-03-22 18:36 ` mpolacek at gcc dot gnu.org
2022-03-22 20:41 ` cvs-commit at gcc dot gnu.org
2022-03-22 20:43 ` mpolacek at gcc dot gnu.org
2022-03-24  9:26 ` yann at droneaud dot fr
2022-03-29  1:46 ` cvs-commit at gcc dot gnu.org [this message]
2022-03-29  1:49 ` 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-82283-4-crezHNewRR@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: link
Be 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).