[Bug preprocessor/79346] New: -Wundef should not warn for standard macros

2017-02-02 Thread mpeg.blue at free dot fr
: preprocessor Assignee: unassigned at gcc dot gnu.org Reporter: mpeg.blue at free dot fr CC: david at westcontrol dot com, jwakely.gcc at gmail dot com, vincent-gcc at vinc17 dot net Target Milestone: --- ML discussion: https://gcc.gnu.org/ml

[Bug c/71552] Confusing error for incorrect struct initialization

2016-06-30 Thread mpeg.blue at free dot fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71552 --- Comment #8 from Mason --- Thanks, Martin. Will your fix be back-ported to gcc 5/6 or will it only be in gcc 7 ? Regards.

[Bug c/71552] Confusing error for incorrect struct initialization

2016-06-18 Thread mpeg.blue at free dot fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71552 --- Comment #5 from Mason --- (In reply to Martin Sebor from comment #3) > In a discussion on gcc-help the submitter provided a different/better test > case for which GCC could and arguably should emit a better error than > "initializer element i

[Bug c/71552] Confusing error for incorrect struct initialization

2016-06-18 Thread mpeg.blue at free dot fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71552 --- Comment #2 from Mason --- Martin, Please reconsider this bug's resolution. In my opinion, "conversion of integers to pointers" is a red herring. This test case (double vs double ptr) triggers the same confusing error: struct foo { double

[Bug c/71552] New: Confusing error for incorrect struct initialization

2016-06-16 Thread mpeg.blue at free dot fr
Component: c Assignee: unassigned at gcc dot gnu.org Reporter: mpeg.blue at free dot fr Target Milestone: --- I'm using gcc version 6.1.1 20160511 (Ubuntu 6.1.1-3ubuntu11~14.04.1) Consider the following code. struct foo { const int *p; }; static const int i = 42; struct fo

[Bug target/64215] New: -Os misses an opportunity to merge two ret instructions

2014-12-07 Thread mpeg.blue at free dot fr
Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: mpeg.blue at free dot fr The following code: int find_mismatch(const char *s, const char *t) { int n; for (n = 0; s[n] == t[n]; ++n) if (s[n] == 0) return -1; return n; } optimized for

[Bug middle-end/64067] ICE in expand_expr_real_1, at expr.c:10540, involving compound literal shenanigans

2014-11-25 Thread mpeg.blue at free dot fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64067 Mason changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment #4 from Mas

[Bug middle-end/64067] ICE in expand_expr_real_1, at expr.c:10540, involving compound literal shenanigans

2014-11-25 Thread mpeg.blue at free dot fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64067 Mason changed: What|Removed |Added Summary|ICE involving compound |ICE in expand_expr_real_1, |li

[Bug middle-end/64067] ICE involving compound literal shenanigans

2014-11-25 Thread mpeg.blue at free dot fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64067 Mason changed: What|Removed |Added CC||polacek at redhat dot com --- Comment #2 from Ma

[Bug middle-end/64067] ICE involving compound literal shenanigans

2014-11-25 Thread mpeg.blue at free dot fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64067 --- Comment #1 from Mason --- Created attachment 34108 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34108&action=edit ICE diagnostic

[Bug middle-end/64067] New: ICE involving compound literal shenanigans

2014-11-25 Thread mpeg.blue at free dot fr
: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: mpeg.blue at free dot fr $ gcc -v -save-temps -O2 test.c Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.8/lto-wrapper Target: x86_64-linux-gnu Configured with: ../src/configure -v