From: "Joseph S. Myers" <joseph@codesourcery.com>
To: "Manuel López-Ibáñez" <lopezibanez@gmail.com>
Cc: Gcc Patch List <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH doc] Explain options precedence and difference between -pedantic-errors and -Werror=pedantic
Date: Sat, 18 Oct 2014 00:04:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1410172338200.14369@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAESRpQBnK_h44iJZMvgs4WCRfM66e-b=9x9V1sjvCofwz3i2Yw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1301 bytes --]
On Sat, 18 Oct 2014, Manuel López-Ibáñez wrote:
> The previous version also does not match your description. You are saying that
>
> -Wpedantic = warning(OPT_Wpedantic) + pedwarn(OPT_Wpedantic)
> and -pedantic-errors = pedwarn(OPT_Wpedantic).+ pedwarn(0)
>
> The current version says that
>
> -Wpedantic = warning(OPT_Wpedantic) + pedwarn(OPT_Wpedantic)
> and -pedantic-errors = warning(OPT_Wpedantic) + pedwarn(OPT_Wpedantic)
>
> My proposal says that:
>
> -Wpedantic = warning(OPT_Wpedantic) + pedwarn(OPT_Wpedantic)
> and -pedantic-errors = warning(OPT_Wpedantic) + pedwarn(OPT_Wpedantic)
> + pedwarn(0)
None of those three descriptions seems helpful here.
The point of -pedantic is to give a diagnostic whenever the standard
requires one (and possibly in some other cases). The point of
-Werror=pedantic is to give an error for diagnostics enabled by -pedantic
(whether or not the standard requires a diagnostic in those cases, and
whether or not the standard requires successful translation in those
cases). The point of -pedantic-errors is to give an error whenever the
standard requires a diagnostic (and possibly in some other cases, but not
cases where the standard requires successful translation).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2014-10-17 23:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 18:40 Manuel López-Ibáñez
2014-10-17 20:53 ` Joseph S. Myers
2014-10-17 23:43 ` Manuel López-Ibáñez
2014-10-18 0:04 ` Joseph S. Myers [this message]
2014-10-18 0:14 ` Manuel López-Ibáñez
2014-10-18 0:41 ` Joseph S. Myers
2014-10-18 17:03 ` Manuel López-Ibáñez
2014-10-19 16:14 ` Joseph S. Myers
2014-10-21 18:26 ` Manuel López-Ibáñez
2014-10-21 22:01 ` Joseph S. Myers
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=Pine.LNX.4.64.1410172338200.14369@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=lopezibanez@gmail.com \
/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).