From: Ian Lance Taylor <iant@google.com>
To: Nick Clifton <nickc@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: gcc --help for options which are not warnings or optimizations
Date: Tue, 02 Jun 2009 13:51:00 -0000 [thread overview]
Message-ID: <m31vq268wy.fsf@google.com> (raw)
In-Reply-To: <4A24F304.5040901@redhat.com> (Nick Clifton's message of "Tue\, 02 Jun 2009 10\:38\:12 +0100")
Nick Clifton <nickc@redhat.com> writes:
> Hi Ian,
>
>> Nick, how is gcc --help supposed to work for options which are neither
>> warnings nor optimizations? For example, -fstack-protector. Is there a
>> --help option which will display it?
>
> Yes - but only the generic "--help --verbose" rather than a more
> qualified version.
In that case I think that gcc --help should display something about
--verbose.
> I suppose we could add another qualifier along the lines of
> "--help=not-otherwise-shown" but that seems rather klunky.
Diego's --help=other suggestion seems reasonable.
Ian
prev parent reply other threads:[~2009-06-02 13:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-01 21:22 Ian Lance Taylor
2009-06-02 9:38 ` Nick Clifton
2009-06-02 12:34 ` Diego Novillo
2009-06-03 7:40 ` Nick Clifton
2009-06-02 13:51 ` Ian Lance Taylor [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=m31vq268wy.fsf@google.com \
--to=iant@google.com \
--cc=gcc@gcc.gnu.org \
--cc=nickc@redhat.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).