https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109475
Jonathan Wakely changed:
What|Removed |Added
Resolution|--- |INVALID
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109475
--- Comment #6 from Jorge Pinto Sousa ---
Let me rephrase, Im sorry maybe I was too broad. For any specific gcc binary,
> /usr/bin/gcc-8 -Q --help=warnings | grep enabled
Will give me the list of warnings enabled by default?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109475
Jorge Pinto Sousa changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109475
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109475
--- Comment #3 from Andrew Pinski ---
>but then some warnings despite being listed there were not triggered:
https://godbolt.org/z/GGnjcjxKh
You get the trigraph warning if you don't supply any options. -std=c++14 option
enables -trigraphs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109475
--- Comment #2 from Jorge Pinto Sousa ---
> No in fact -Wformat-security is not enabled by default in the released
> version of GCC from the FSF, the distro I know that enables it by default is
> both Debian and Ubuntu.
Ah so the ones that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109475
--- Comment #1 from Andrew Pinski ---
>So we can say that these are the only two that are default enabled?
No in fact -Wformat-security is not enabled by default in the released version
of GCC from the FSF, the distro I know that enables it
