From: Nick Clifton <nickc@redhat.com>
To: Diego Novillo <dnovillo@google.com>, Ian Lance Taylor <iant@google.com>
Cc: gcc@gcc.gnu.org
Subject: Re: gcc --help for options which are not warnings or optimizations
Date: Wed, 03 Jun 2009 07:40:00 -0000 [thread overview]
Message-ID: <4A2628F0.2060708@redhat.com> (raw)
In-Reply-To: <b798aad50906020533w43d84663r9ca0a0f50cf70211@mail.gmail.com>
Hi Ian, Hi Diego,
> Diego Novillo wrote:
> --help=other?
That works. :-)
Actually, there already is a qualifier which will select
-fstack-protector, I had just forgotten about it:
% gcc --help=common | grep stack
-Wstack-protector Warn when not issuing stack smashing
protection
-fdefer-pop Defer popping functions args from stack until
-fomit-frame-pointer When possible do not generate stack frames
-fstack-check Insert stack checking code into the program
-fstack-limit This switch lacks documentation
-fstack-limit-register=<register> Trap if the stack goes past <register>
-fstack-limit-symbol=<name> Trap if the stack goes past symbol <name>
-fstack-protector Use propolice as a stack protection method
-fstack-protector-all Use a stack protection method for every
function
Cheers
Nick
next prev parent reply other threads:[~2009-06-03 7:40 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 [this message]
2009-06-02 13:51 ` Ian Lance Taylor
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=4A2628F0.2060708@redhat.com \
--to=nickc@redhat.com \
--cc=dnovillo@google.com \
--cc=gcc@gcc.gnu.org \
--cc=iant@google.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).