From: Bruno Haible <bruno@clisp.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: bug-gnulib@gnu.org
Subject: Re: stack bounds
Date: Mon, 12 Oct 2020 00:08:59 +0200 [thread overview]
Message-ID: <44517174.0iPovtODdz@omega> (raw)
In-Reply-To: <49ddabf6-57ff-146d-de09-e1c6c187308f@cs.ucla.edu>
Paul Eggert wrote:
> That being said, it does look like a reliability win if we start using
> -fstack-clash-protection on platforms like Fedora x86-64 that support it and do
> not enable it by default. Perhaps we should have a Gnulib or Autoconf macro that
> does that.
Yes, such a macro would be useful. To be used at the discretion of the package
maintainer (e.g. through a Gnulib module, similar to the 'largefile' module).
But do you have an overview which targets are meant in the doc?
"old-style stack checking is also the fallback method for ‘specific’ if no
target support has been added in the compiler."
"Most targets do not fully support stack clash protection."
Bruno
next prev parent reply other threads:[~2020-10-11 22:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m2a6xnu1sv.fsf@meyering.net>
[not found] ` <075a970b-f6aa-d2bb-e007-609a711085b2@gmail.com>
[not found] ` <CA+8g5KGBjFfHzafN2WFH6az5bQR8f68B1J-ETVWEBXvuDUL5rA@mail.gmail.com>
[not found] ` <17a0fe42-3ac6-9209-6f60-cddb5467f263@gmail.com>
[not found] ` <994fd316-0420-4b94-a1de-fea7d891c4ac@gmail.com>
2020-09-18 22:16 ` new snapshot available: grep-3.4-almost.26-5419 Paul Eggert
2020-09-18 22:42 ` Bruce Dubbs
2020-09-18 23:24 ` libsigsegv on LinuxFromScratch Bruno Haible
2020-09-18 23:47 ` Bruce Dubbs
2020-09-19 8:06 ` Bruce Dubbs
2020-09-19 23:47 ` Bruno Haible
2020-09-20 1:16 ` Bruce Dubbs
2020-09-20 23:15 ` Paul Eggert
2020-09-23 0:58 ` stack bounds Bruno Haible
2020-09-23 1:28 ` Paul Eggert
2020-10-10 12:08 ` Bruno Haible
2020-10-10 20:10 ` Paul Eggert
2020-10-10 21:49 ` Bruno Haible
2020-10-11 18:49 ` Paul Eggert
2020-10-11 22:08 ` Bruno Haible [this message]
2020-10-11 22:56 ` Paul Eggert
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44517174.0iPovtODdz@omega \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
/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).