public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "eric dot estievenart at free dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/44210] New: Extended warning control: like -Wevery -show-warnings
Date: Thu, 20 May 2010 11:46:00 -0000 [thread overview]
Message-ID: <bug-44210-19151@http.gcc.gnu.org/bugzilla/> (raw)
As I always wonder if my compiler could help me find more bugs,
and the list of warnings I enable tend to be very long,
and -Wall is not enough for me...
(This bug certainly depends on #44209: "Some warnings are not linked to
diagnostics options")
It would be great to have the following options:
(I really don't care for their names if you have better suggestions;
I focus on the functionality)
-Wevery: would enable all warnings known to gcc
================================================
This would allow reducing this (infamous) list:
-W -Wall -Wextra -Wstrict-aliasing=2 -Wfloat-equal -Wundef -Wconversion
-Winline -Wmissing-field-initializers -Wshadow -Wcast-align -Wformat=2
-Wsequence-point -Woverloaded-virtual
(I never know which one is enabled by -W, -Wall, -Wextra...)
to a single -Wevery with a few -Wno-XXXXXX
-show-warnings: would show the enabled warnings
================================================
An example usage would be:
$ gcc -c somefile.c -Wall -Werror -Wno-error=reorder -Wno-unused-function
..... -show-warnings
status name from
------------------------------------------------
ERROR address -Wall -Werror
warn reorder -Wall -Werror -Wno-error=reorder
- unused-function -Wno-unused-function
- clobbered (would be enabled by -Wextra)
...
------------------------------------------------
372 known warnings, 300 shown, 297 as errors (muted: 72)
If the team is interested, I'll consider providing a patch.
--
Summary: Extended warning control: like -Wevery -show-warnings
Product: gcc
Version: 4.5.0
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: driver
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: eric dot estievenart at free dot fr
GCC build triplet: does not apply
GCC host triplet: does not apply
GCC target triplet: does not apply
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44210
next reply other threads:[~2010-05-20 11:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 11:46 eric dot estievenart at free dot fr [this message]
2010-05-20 13:31 ` [Bug driver/44210] " redi at gcc dot gnu dot org
2010-05-20 15:07 ` eric dot estievenart at free dot fr
2010-05-20 16:15 ` [Bug other/44210] " redi at gcc dot gnu dot org
2010-05-20 17:04 ` manu at gcc dot gnu dot org
2010-05-21 18:00 ` eric dot estievenart at free dot fr
2010-05-22 0:32 ` manu at gcc dot gnu dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-44210-19151@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).