https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61276
Andrew Pinski changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61276
Marek Polacek changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61276
--- Comment #6 from joseph at codesourcery dot com ---
You could suggest GCC diagnostic issues to
http://www.linuxfoundation.org/programs/core-infrastructure-initiative if
you wish
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61276
Jonathan Wakely changed:
What|Removed |Added
Keywords||diagnostic
--- Comment #5 from Jonatha
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61276
--- Comment #4 from Manuel López-Ibáñez ---
(In reply to David Binderman from comment #2)
> It would also find an unknown number of bugs in Linux kernel,
> which compiles with gcc only, sadly.
Which I find sad is that GCC does not have such a si
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61276
--- Comment #3 from Manuel López-Ibáñez ---
Just to mention that I cloned PR 61271 to not forget about implementing the
warning once the problematic code is fixed. So this PR should be about
implementing the warning, rather than fixing any partic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61276
--- Comment #2 from David Binderman ---
(In reply to Manuel López-Ibáñez from comment #0)
> GCC should have this warning which would have detected several obvious bugs
> in GCC itself.
And at least 60 bugs in Fedora Linux, based on compiling
Fed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61276
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
