public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "david at doublewise dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/53313] Add warning levels Date: Fri, 24 Apr 2015 01:16:00 -0000 [thread overview] Message-ID: <bug-53313-4-aoUTCNKpe7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53313-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53313 --- Comment #8 from David Stone <david at doublewise dot net> --- I have changed my opinion on this and agree that warning levels are probably not the way to go. The two things from this that I do still want are -Weverything-and-I-really-mean-it-this-time All warnings either warn for exactly one type of thing or they turn on other warnings that themselves can be individually turned on or off.
next prev parent reply other threads:[~2015-04-24 1:16 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-10 22:00 [Bug other/53313] New: " DeusExSophismata at gmail dot com 2012-05-10 22:04 ` [Bug other/53313] " DeusExSophismata at gmail dot com 2012-08-16 3:49 ` david at doublewise dot net 2012-09-30 7:24 ` jan.kratochvil at redhat dot com 2012-09-30 13:16 ` manu at gcc dot gnu.org 2012-12-08 17:59 ` glisse at gcc dot gnu.org 2014-03-17 10:37 ` slyfox at inbox dot ru 2015-04-22 16:13 ` manu at gcc dot gnu.org 2015-04-24 1:16 ` david at doublewise dot net [this message] 2015-04-24 10:29 ` manu at gcc dot gnu.org 2015-04-24 11:59 ` glisse at gcc dot gnu.org 2015-04-24 13:53 ` david at doublewise dot net 2015-04-24 14:22 ` redi at gcc dot gnu.org 2015-04-25 15:10 ` david at doublewise dot net
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-53313-4-aoUTCNKpe7@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: linkBe 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).