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: Tue, 21 Oct 2014 22:01:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1410212157430.24064@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAESRpQBm0aXJprWxKZFv+XcfATej2=iXw1L3GfRErLWMwqXUzw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 987 bytes --]
On Tue, 21 Oct 2014, Manuel López-Ibáñez wrote:
> On 19 October 2014 18:08, Joseph S. Myers <joseph@codesourcery.com> wrote:
> > On Sat, 18 Oct 2014, Manuel López-Ibáñez wrote:
> >
> >> What about this version?
> >>
> >> Give an error whenever the @dfn{base standard} (see @option{-Wpedantic})
> >> requires a diagnostic, in cases where there is undefined behavior at
> >> compile-time
> >
> > Only in *some* such cases of compile-time undefined behavior.
>
> New try:
>
> Give an error whenever the @dfn{base standard} (see @option{-Wpedantic})
> requires a diagnostic, in some cases where there is undefined behavior at
> compile-time and in some other cases that do not prevent compilation of programs
> that are valid according to the standard. This is not equivalent to
> @option{-Werror=pedantic}, since there are errors enabled by this option
> and not enabled by the latter and vice versa.
>
> OK?
OK.
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2014-10-21 21:58 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
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 [this message]
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.1410212157430.24064@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).