[Bug c/82283] Wrong warning with -Wmissing-field-initializers

2022-03-28 Thread mpolacek at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82283 Marek Polacek changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[Bug c/82283] Wrong warning with -Wmissing-field-initializers

2022-03-28 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82283 --- Comment #17 from CVS Commits --- The releases/gcc-11 branch has been updated by Marek Polacek : https://gcc.gnu.org/g:0fa9022aa30b9c4dde965a0406943c8c0af5eb54 commit r11-9715-g0fa9022aa30b9c4dde965a0406943c8c0af5eb54 Author: Marek Polacek

[Bug c/82283] Wrong warning with -Wmissing-field-initializers

2022-03-24 Thread yann at droneaud dot fr via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82283 --- Comment #16 from Yann Droneaud --- (In reply to Marek Polacek from comment #13) > I have a patch which fixes all the testcases here. I've checked my test cases using godbolt gcc trunk, and, yeah, thanks a lot !

[Bug c/82283] Wrong warning with -Wmissing-field-initializers

2022-03-22 Thread mpolacek at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82283 --- Comment #15 from Marek Polacek --- Patch seems safe to backport to 11.

[Bug c/82283] Wrong warning with -Wmissing-field-initializers

2022-03-22 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82283 --- Comment #14 from CVS Commits --- The trunk branch has been updated by Marek Polacek : https://gcc.gnu.org/g:4b7d9f8f51bd96d290aac230c71e501fcb6b21a6 commit r12-7772-g4b7d9f8f51bd96d290aac230c71e501fcb6b21a6 Author: Marek Polacek Date:

[Bug c/82283] Wrong warning with -Wmissing-field-initializers

2022-03-22 Thread mpolacek at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82283 Marek Polacek changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |mpolacek at gcc dot gnu.org

[Bug c/82283] Wrong warning with -Wmissing-field-initializers

2022-02-04 Thread rsandifo at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82283 rsandifo at gcc dot gnu.org changed: What|Removed |Added CC||rsandifo at gcc dot

[Bug c/82283] Wrong warning with -Wmissing-field-initializers

2021-04-14 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82283 --- Comment #11 from Jonathan Wakely --- (In reply to Robert Dumitru from comment #10) > I think https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99081 is also relating > to this. A similar issue, but I think the code for parsing these initializes

[Bug c/82283] Wrong warning with -Wmissing-field-initializers

2021-04-14 Thread robert.dumitru at cyberthorstudios dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82283 Robert Dumitru changed: What|Removed |Added CC||robert.dumitru@cyberthorstu

[Bug c/82283] Wrong warning with -Wmissing-field-initializers

2020-05-12 Thread marxin at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82283 Martin Liška changed: What|Removed |Added CC||marxin at gcc dot gnu.org,

[Bug c/82283] Wrong warning with -Wmissing-field-initializers

2020-02-24 Thread yann at droneaud dot fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82283 --- Comment #8 from Yann Droneaud --- See also this stack overflow question https://stackoverflow.com/questions/49081541/compound-literal-and-designated-initializer-warning-from-gcc-but-not-clang

[Bug c/82283] Wrong warning with -Wmissing-field-initializers

2020-02-24 Thread yann at droneaud dot fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82283 --- Comment #7 from Yann Droneaud --- See also bug #84685 which is a very likely duplicate of this one.

[Bug c/82283] Wrong warning with -Wmissing-field-initializers

2020-02-24 Thread yann at droneaud dot fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82283 --- Comment #6 from Yann Droneaud --- Found this one on stack overflow[1], and I find it a bit embarrassing: struct { struct { int a; int b; } c[1]; } d = { .c[0].a = 1, .c[0].b = 1, };

[Bug c/82283] Wrong warning with -Wmissing-field-initializers

2020-02-23 Thread yann at droneaud dot fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82283 --- Comment #5 from Yann Droneaud --- For a full combo, here's the almost original code that trigger the two errors above with GLibc < 2.28, only one with newer Glibc. #define _GNU_SOURCE 1 #include #include #include

[Bug c/82283] Wrong warning with -Wmissing-field-initializers

2020-02-22 Thread yann at droneaud dot fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82283 --- Comment #4 from Yann Droneaud --- Also with the ({}) GCC extension: struct a { int b; int c; }; void d(struct a *); void e(void) { struct a f = { .b = ({

[Bug c/82283] Wrong warning with -Wmissing-field-initializers

2020-02-22 Thread yann at droneaud dot fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82283 Yann Droneaud changed: What|Removed |Added CC||yann at droneaud dot fr --- Comment #3

[Bug c/82283] Wrong warning with -Wmissing-field-initializers

2019-01-07 Thread egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82283 Eric Gallager changed: What|Removed |Added CC||dmalcolm at gcc dot gnu.org,

[Bug c/82283] Wrong warning with -Wmissing-field-initializers

2017-09-28 Thread egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82283 Eric Gallager changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|