https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66966
--- Comment #8 from Manuel López-Ibáñez ---
(In reply to Anders Granlund from comment #7)
> OK. Seems to work differently in Clang but I guess they don't have the same
> problem with legacy.
Changing defaults in GCC to match Clang is possible (w
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66966
Anders Granlund changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66966
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=66966
Anders Granlund changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|INVALID
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66966
--- Comment #4 from Anders Granlund ---
(In reply to Jonathan Wakely from comment #2)
> Oh wait ... if you use -w then you are suppressing diagnostics, so you can't
> really complain that there are no diagnostics!
>
> So this seems invalid to me
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66966
--- Comment #3 from Anders Granlund ---
(In reply to Jonathan Wakely from comment #2)
> Oh wait ... if you use -w then you are suppressing diagnostics, so you can't
> really complain that there are no diagnostics!
>
> So this seems invalid to me
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66966
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66966
Jonathan Wakely changed:
What|Removed |Added
Keywords||accepts-invalid
Status|UNC
