public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/44774] -Werror=edantic
Date: Fri, 02 Jul 2010 01:23:00 -0000 [thread overview]
Message-ID: <20100702012255.7726.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44774-13511@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from joseph at codesourcery dot com 2010-07-02 01:22 -------
Subject: Re: -Werror=edantic
On Thu, 1 Jul 2010, manu at gcc dot gnu dot org wrote:
> We also should add a -Wpedantic-default (or -Wpedantic-required) for pedwarns
> enabled by default (not by -pedantic).
Those would be extremely bad option names, since diagnostics enabled by
default have nothing to do with pedantry; "pedwarn" is simply a
GCC-internal function name for diagnosing constraint violations and should
not be allowed to influence command-line option names. -pedantic-errors
means something like -Werror=standard-required-diagnostics and a pedwarn
enabled by default is a standard-required diagnostic enabled by default
(as opposed to a warning enabled by default which is a
non-standard-required diagnostic enabled by default). There is no
particular reason to allow people to disable standard-required default
diagnostics as a group separately from non-standard-required ones; think
about more useful classifications of the existing enabled-by-default
diagnostics to work out suitable option names for disabling them.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44774
next prev parent reply other threads:[~2010-07-02 1:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 21:40 [Bug c/44774] New: -Werror=edantic manu at gcc dot gnu dot org
2010-07-01 21:42 ` [Bug c/44774] -Werror=edantic manu at gcc dot gnu dot org
2010-07-01 21:54 ` manu at gcc dot gnu dot org
2010-07-02 1:23 ` joseph at codesourcery dot com [this message]
2010-07-02 6:59 ` manu at gcc dot gnu dot org
2010-07-02 8:08 ` manu at gcc dot gnu dot org
2010-07-02 9:22 ` jakub at gcc dot gnu dot org
2010-07-02 10:56 ` manu at gcc dot gnu dot org
2010-07-02 12:18 ` paolo dot carlini at oracle dot com
2010-07-02 14:24 ` manu at gcc dot gnu dot org
2010-07-02 15:22 ` paolo dot carlini at oracle dot com
2010-07-04 1:46 ` joseph at codesourcery dot com
2010-07-04 8:27 ` manu at gcc dot gnu dot org
[not found] <bug-44774-4@http.gcc.gnu.org/bugzilla/>
2011-03-23 9:35 ` redi at gcc dot gnu.org
2011-04-19 15:17 ` redi at gcc dot gnu.org
2012-02-17 0:35 ` manu at gcc dot gnu.org
2012-04-22 19:18 ` manu at gcc dot gnu.org
2012-04-22 19:58 ` manu at gcc dot gnu.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=20100702012255.7726.qmail@sourceware.org \
--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).