public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@mengyan1223.wang>
To: Reinoud Koornstra <reinoudkoornstra@gmail.com>,
	Florian Weimer <fweimer@redhat.com>
Cc: Reinoud Koornstra via Gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Fortify_source and stack-protector-strong
Date: Thu, 03 Mar 2022 03:46:21 +0800	[thread overview]
Message-ID: <2a574a7a0dbb4f1ef4472d2a43b029f0ceca9065.camel@mengyan1223.wang> (raw)
In-Reply-To: <CAAA5faGBqtp0=00Mi+7Cvk3nLuV_CpD7jT4OAJ4k7NxaFcb-5g@mail.gmail.com>

On Wed, 2022-03-02 at 11:09 -0800, Reinoud Koornstra via Gcc-help wrote:
> Hi Florian,
> 
> Thanks very much for your reply.
> -D_FORTIFY_SOURCE=1 is just during compile time and -D_FORTIFY_SOURCE=2
> also has runtime checks for variable length?

Both -D_FORTIFY_SOURCE=1 and -D_FORTIFY_SOURCE=2 determine buffer size
at compile time.  But they are runtime checks: the input size is
compared with the buffer size at runtime.  They are not a pure compile-
time checking like -Wstringop-overflow.

-D_FORTIFY_SOURCE=3 supports runtime calculation of variable-length
buffer, but it needs Glibc >= 2.35 and GCC >= 12.0 (not released yet).
-- 
Xi Ruoyao <xry111@mengyan1223.wang>
School of Aerospace Science and Technology, Xidian University

  reply	other threads:[~2022-03-02 19:46 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 [this message]
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=2a574a7a0dbb4f1ef4472d2a43b029f0ceca9065.camel@mengyan1223.wang \
    --to=xry111@mengyan1223.wang \
    --cc=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).