https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67314
Eric Gallager changed:
What|Removed |Added
Last reconfirmed|2016-01-16 00:00:00 |2019-11-20
--- Comment #8 from Eric Gall
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67314
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
S
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67314
--- Comment #6 from Manuel López-Ibáñez ---
(In reply to Martin Sebor from comment #4)
> The trouble is that while gcc
> makes it easy to assign without a warning values to enums that are outside
> the range of the enumerated type, it makes it di
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67314
Eric Gallager changed:
What|Removed |Added
CC||egall at gwmail dot gwu.edu
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67314
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67314
Manuel López-Ibáñez changed:
What|Removed |Added
CC||manu at gcc dot gnu.org
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67314
--- Comment #2 from Chengnian Sun ---
(In reply to Andrew Pinski from comment #1)
> This warning is only useful for c++. C defines the full range of the
> underlying type of the enum for the enum while c++ has different rules.
>
> Also I think
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67314
--- Comment #1 from Andrew Pinski ---
This warning is only useful for c++. C defines the full range of the underlying
type of the enum for the enum while c++ has different rules.
Also I think this warning would be too noisy for c code and clang
