From: Florian Weimer <fweimer@redhat.com>
To: Reinoud Koornstra <reinoudkoornstra@gmail.com>
Cc: Xi Ruoyao <xry111@mengyan1223.wang>,
Reinoud Koornstra via Gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Fortify_source and stack-protector-strong
Date: Tue, 19 Apr 2022 13:24:56 +0200 [thread overview]
Message-ID: <87tuap2u47.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAAA5faGO5pY36sR4gn83+mE40kRGXVCFohTLgxCzBsOpzC8d8Q@mail.gmail.com> (Reinoud Koornstra's message of "Fri, 11 Mar 2022 11:01:05 -0800")
* Reinoud Koornstra:
> One more question, for FORTIFY_SOURCE=2, can I use either -O1 or -O2
> optimization flags? I noticed it doesn't like -Os. Thanks,
Historically, I think the expectation was that 1 should be used with -O1
and 2 with -O2. But I think the required passes run at -O1 as well.
Thanks,
Florian
prev parent reply other threads:[~2022-04-19 11:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 23:23 Reinoud Koornstra
2022-03-02 10:22 ` Florian Weimer
2022-03-02 19:09 ` Reinoud Koornstra
2022-03-02 19:46 ` Xi Ruoyao
2022-03-02 20:05 ` Reinoud Koornstra
2022-03-02 20:23 ` Xi Ruoyao
2022-03-02 20:45 ` Reinoud Koornstra
2022-03-11 19:01 ` Reinoud Koornstra
2022-03-12 8:19 ` Xi Ruoyao
2022-04-19 11:24 ` Florian Weimer [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=87tuap2u47.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=gcc-help@gcc.gnu.org \
--cc=reinoudkoornstra@gmail.com \
--cc=xry111@mengyan1223.wang \
/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).