[Bug c/120710] C23 enum member does not have during processing the type indicated by C23 6.7.3.3:12

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120710 Pascal Cuoq changed: What|Removed |Added Summary|C23 enum member does not|C23 enum member does not

[Bug c/120710] New: C23 enum member does not have during processing the type indicated by C23 6.7.3.4:12

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120710 Bug ID: 120710 Summary: C23 enum member does not have during processing the type indicated by C23 6.7.3.4:12 Product: gcc Version: 15.1.0 Status: UNCONFIRMED S

[Bug c/96788] "integer constant is so large that it is unsigned" warning is incorrect

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96788 --- Comment #11 from Pascal Cuoq --- @newbie-02 Sir, this is the GCC bugzilla. You have to contact your national standardization institute so that they convey your suggestions to ISO. Incidentally, while it is subjective whether the individual

[Bug c/109956] GCC reserves 9 bytes for struct s { int a; char b; char t[]; } x = {1, 2, 3};

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109956 --- Comment #13 from Pascal Cuoq --- @Martin I completely agree with comment 12, however about the last paragraph, I would like to point out that for purposes of memcpy'ing to or from such a struct with initialized FAM, it is enough to recommen

[Bug c/109956] GCC reserves 9 bytes for struct s { int a; char b; char t[]; } x = {1, 2, 3};

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109956 --- Comment #3 from Pascal Cuoq --- @Andrew Pinski You don't even need to invoke the fact that this is an extension. GCC could reserve 17 bytes for each variable i of type “int”, and as long as “sizeof i” continued to evaluate to 4 (4 being the

[Bug c/109956] New: GCC reserves 9 bytes for struct s { int a; char b; char t[]; } x = {1, 2, 3};

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109956 Bug ID: 109956 Summary: GCC reserves 9 bytes for struct s { int a; char b; char t[]; } x = {1, 2, 3}; Product: gcc Version: 14.0 Status: UNCONFIRMED Severity:

[Bug c/104607] Struct padding not initialized when all members are provided initializers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104607 --- Comment #2 from Pascal Cuoq --- Well that's a quick resolution to a bug report that contained that actual phrase “and any padding is initialized to zero bits”, and this in a quote from the C11 standard, but I guess one of us can't read then.

[Bug c/104607] New: Struct padding not initialized when all members are provided initializers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104607 Bug ID: 104607 Summary: Struct padding not initialized when all members are provided initializers Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: norm

[Bug c/97986] New: ICE in force_constant_size when applying va_arg to VLA type

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97986 Bug ID: 97986 Summary: ICE in force_constant_size when applying va_arg to VLA type Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Pri

[Bug c/96788] "integer constant is so large that it is unsigned" warning is incorrect

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96788 Pascal Cuoq changed: What|Removed |Added CC||pascal_cuoq at hotmail dot com --- Comment