public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Reinoud Koornstra via Gcc-help <gcc-help@gcc.gnu.org>
Cc: Reinoud Koornstra <reinoudkoornstra@gmail.com>
Subject: Re: Fortify_source and stack-protector-strong
Date: Wed, 02 Mar 2022 11:22:45 +0100	[thread overview]
Message-ID: <87o82ok616.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAAA5faFWb6xz2mJ0LzRTxRHARq9vdmF+4bChWWEZCuW+uCNB4Q@mail.gmail.com> (Reinoud Koornstra via Gcc-help's message of "Tue, 1 Mar 2022 15:23:08 -0800")

* Reinoud Koornstra via Gcc-help:

> Is it possible to compile with -stack-protector-strong and
> FORTIFY_SOURCE=1 or =2?  Or should both be used exclusively from
> another? Both check for similar things.

They complement each other.  I think most distributions use both these
days (-fstack-protector-strong and -D_FORTIFY_SOURCE=2).

Thanks,
Florian


  reply	other threads:[~2022-03-02 10:22 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 [this message]
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

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=87o82ok616.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=reinoudkoornstra@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).