https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86134
Richard Biener changed:
What|Removed |Added
CC||vincent-gcc at vinc17 dot net
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86134
Richard Biener changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86134
--- Comment #13 from CVS Commits ---
The master branch has been updated by Richard Guenther :
https://gcc.gnu.org/g:abe13e1847fb91d43f02b5579c4230214d4369f4
commit r10-6668-gabe13e1847fb91d43f02b5579c4230214d4369f4
Author: Richard Biener
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86134
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86134
--- Comment #11 from Pádraig Brady ---
I agree that -Wno-... should never be promoted to an error as we see with:
$ echo 'int maint(){}' | gcc -S -x c -Wno-unknown-warning-option -Wall -Werror
-Wextra -Wno-error=return-type -
: In function
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86134
--- Comment #10 from joseph at codesourcery dot com ---
On Fri, 15 Jun 2018, rguenth at gcc dot gnu.org wrote:
> Joseph, do you agree that the following shouldn't fail the compilation?
>
> > echo 'int main(){}' | gcc -S -x c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86134
--- Comment #9 from Manuel López-Ibáñez ---
That makes sense as well. Adding further logic to silence the warning or to
make the warning not become an error is what I think is a bad idea. I like
also your more explicit wording.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86134
--- Comment #8 from rguenther at suse dot de ---
On Fri, 15 Jun 2018, lopezibanez at gmail dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86134
>
> --- Comment #7 from Manuel López-Ibáñez ---
> What I'm suggesting is to add an
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86134
--- Comment #7 from Manuel López-Ibáñez ---
What I'm suggesting is to add an option to control this warning, which is
currently enabled by default. Then you can use -Wno-error or even -Wno- to
make it always a warning or completely disable it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86134
Richard Biener changed:
What|Removed |Added
CC||jsm28 at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86134
Manuel López-Ibáñez changed:
What|Removed |Added
CC||manu at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86134
--- Comment #4 from rguenther at suse dot de ---
On Wed, 13 Jun 2018, msebor at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86134
>
> --- Comment #3 from Martin Sebor ---
> As per the recent discussion:
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86134
--- Comment #3 from Martin Sebor ---
As per the recent discussion:
https://gcc.gnu.org/ml/gcc-patches/2018-06/msg00422.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86134
Martin Sebor changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86134
Richard Biener changed:
What|Removed |Added
Summary|earlier error causes|earlier diagnostic causes
15 matches
Mail list logo
