public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: gcc-patches@gcc.gnu.org, fortran@gcc.gnu.org
Subject: Re: [PATCH] Fix -W* documentation, update to 	contrib/check_warning_flags.sh
Date: Sun, 09 Mar 2008 17:43:00 -0000	[thread overview]
Message-ID: <20080309174311.GT6280@ins.uni-bonn.de> (raw)
In-Reply-To: <alpine.LSU.1.00.0803082208420.22304@acrux.dbai.tuwien.ac.at>

Hello Gerald,

* Gerald Pfeifer wrote on Sat, Mar 08, 2008 at 10:12:40PM CET:
> On Sat, 8 Mar 2008, Ralf Wildenhues wrote:
> > PING^2 <http://gcc.gnu.org/ml/gcc-patches/2008-02/msg00882.html>
> > OK for trunk also for the non-Fortran bits?
> 
> Yep.  The one to c.opt looks obvious, and the rest is just docs.

Thanks, committed.

> +@item -Wno-format-contains-nul
> +@opindex Wno-format-contains-nul
> +@opindex Wformat-contains-nul
> +If @option{-Wformat} is specified, do not warn about format strings that
> +contain NUL bytes.
> 
> I guess if someone really wanted to, she could use -Wformat-contains-nul 
> alone (without -Wformat) as well, right?

Yes, but this formulation is just in line with how
-Wno-format-extra-args and -Wno-format-zero-length are described, too.
Terse, but not illogical, no?

Cheers,
Ralf

  reply	other threads:[~2008-03-09 17:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-20 21:32 Ralf Wildenhues
2008-02-20 23:42 ` FX Coudert
2008-02-26 22:24 ` Ralf Wildenhues
2008-03-08 13:25 ` Ralf Wildenhues
2008-03-08 21:13   ` Gerald Pfeifer
2008-03-09 17:43     ` Ralf Wildenhues [this message]
2008-03-16 23:49       ` Gerald Pfeifer

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=20080309174311.GT6280@ins.uni-bonn.de \
    --to=ralf.wildenhues@gmx.de \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.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).