https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31350
Manuel López-Ibáñez changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31350
--- Comment #6 from Manuel López-Ibáñez ---
This is exactly the same case as:
$ gcc --help --invalid 1> /dev/null
gcc: error: unrecognized command line option ‘--invalid’
One should not expect the error output to go to stdout just because --hel
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82448
--- Comment #2 from Andrew Pinski ---
(In reply to Jonathan Wakely from comment #1)
> Note that -Werror= does work for most warnings, just not for
> -Wsequence-point. This is simply a bug in the old release, which has been
> fixed in current rele
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82457
Andrew Pinski changed:
What|Removed |Added
Keywords||documentation
Status|UNCONFI
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50410
--- Comment #30 from Jerry DeLisle ---
(In reply to Dominique d'Humieres from comment #28)
--- snip ---
> BTW what is the best expression in English "already is" or "is already", the
> later being easier to parse for French readers.
"is already"
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82457
Andrew Schepler changed:
What|Removed |Added
CC||aschepler at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82457
--- Comment #3 from Andrew Pinski ---
(In reply to Andrew Schepler from comment #2)
> I don't follow your explanation. In standard-compliant mode, the compiler
> isn't allowed to change the behavior of a function because it's NOT specifed
> by a
101 - 107 of 107 matches
Mail list logo
