https://gcc.gnu.org/bugzilla/show_bug.cgi?id=16186
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #8
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=16186
trashyankes at wp dot pl changed:
What|Removed |Added
CC||trashyankes at wp dot pl
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=16186
Martin Liška changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=16186
Marek Polacek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=16186
--- Comment #4 from Martin Liška ---
(In reply to Marek Polacek from comment #3)
> FWIW, Clang implements this warning:
Oh, I was unable to find the option (only tried -Werror and -Wextra).
@Marek: please add it!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=16186
--- Comment #3 from Marek Polacek ---
FWIW, Clang implements this warning:
$ xclang++ -c -xc j.c -Wduplicate-enum
j.c:1:33: warning: element 'foo' has been implicitly assigned 0 which another
element has been assigned [-Wduplicate-enum]
enum
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=16186
Andrew Pinski changed:
What|Removed |Added
CC||marxin at gcc dot gnu.org
--- Comment
