https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69864
--- Comment #15 from Eric Gallager ---
(In reply to Manuel López-Ibáñez from comment #8)
[...snip...]
> and replace the kludge in cp/typeck2.c with it (possibly fixing PR69872
> along the way). Document when some warnings might be errors (like we
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69864
Jonathan Wakely changed:
What|Removed |Added
CC|redi at gcc dot gnu.org|
--- Comment #14 from Jonathan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69864
Eric Gallager changed:
What|Removed |Added
Keywords|documentation |
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69864
--- Comment #12 from Jonathan Wakely ---
(In reply to Jonathan Wakely from comment #11)
> Patch: https://gcc.gnu.org/ml/gcc-patches/2016-02/msg01326.html
Committed to trunk.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69864
--- Comment #11 from Jonathan Wakely ---
(In reply to Manuel López-Ibáñez from comment #8)
> I'm actually going to reopen this to propose some improvements that perhaps
> someone would decide to tackle as easy hacks:
>
> * Document that -Wnarrow
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69864
--- Comment #10 from Manuel López-Ibáñez ---
(In reply to Markus Trippelsdorf from comment #9)
> > * Create a new function in diagnostic.c, e.g.,
> >
> > extern diagnostic_t pederror (location_t, int, const char *, ...)
> > ATTRIBUTE_GCC_D
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69864
--- Comment #9 from Markus Trippelsdorf ---
(In reply to Manuel López-Ibáñez from comment #8)
> (In reply to Jonathan Wakely from comment #6)
> > Because int b{2.3} absolutely definitely loses precision, and since it's a
> > constant you can just
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69864
Manuel López-Ibáñez changed:
What|Removed |Added
Keywords||diagnostic, documentation,
