https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71552
--- Comment #9 from Martin Sebor ---
I asked on the list and it doesn't seem that this rises to the level of
importance to justify backporting it (as regressions or incorrect code
generation do).
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.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71552
Martin Sebor changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71552
--- Comment #6 from Martin Sebor ---
Author: msebor
Date: Tue Jun 28 20:09:36 2016
New Revision: 237829
URL: https://gcc.gnu.org/viewcvs?rev=237829&root=gcc&view=rev
Log:
PR c/71552 - Confusing error for incorrect struct initialization
gcc/c/Ch
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71552
Martin Sebor changed:
What|Removed |Added
Status|RESOLVED|ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71552
--- Comment #4 from Martin Sebor ---
Patch posted for review:
https://gcc.gnu.org/ml/gcc-patches/2016-06/msg01357.html
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71552
Martin Sebor changed:
What|Removed |Added
Keywords||diagnostic
Status|UNCONFIRMED
