From: Mark Wielaard <mark@klomp.org>
To: Martin Sebor <msebor@gmail.com>
Cc: Graham Markall <graham.markall@embecosm.com>,
David Brown <david.brown@hesbynett.no>,
Segher Boessenkool <segher@kernel.crashing.org>,
P J P <pj.pandit@yahoo.co.in>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: About BZ#87210 [RFE] To initialize automatic stack variables
Date: Tue, 05 Mar 2019 23:08:00 -0000 [thread overview]
Message-ID: <20190305230829.GA62096@wildebeest.org> (raw)
In-Reply-To: <8ae52ac6-9b7b-8f16-725b-808f38aa779a@gmail.com>
On Tue, Mar 05, 2019 at 02:17:51PM -0700, Martin Sebor wrote:
> The SECURE project adds the function attribute stack_erase that
> serves the purpose described above. It works on stack frames by
> design rather than applying to individual stack objects.
> The presentation they delivered at Cauldron 2018 made it sound
> like they were on track for submitting the feature to GCC:
>
> https://www.youtube.com/watch?v=Lg_jJLtH7R0
The slides of that talk can be found here:
https://gmarkall.files.wordpress.com/2018/09/secure_and_gcc.pdf
next prev parent reply other threads:[~2019-03-05 23:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1225413012.1679387.1550571810991.ref@mail.yahoo.com>
2019-02-19 10:24 ` P J P
2019-03-04 10:44 ` P J P
2019-03-04 12:02 ` Richard Biener
2019-03-04 20:46 ` David Brown
2019-03-05 18:37 ` Segher Boessenkool
2019-03-05 20:37 ` David Brown
2019-03-05 21:17 ` Martin Sebor
2019-03-05 23:08 ` Mark Wielaard [this message]
2019-03-06 1:51 ` Segher Boessenkool
2019-03-06 13:11 ` David Brown
2019-03-06 13:43 ` Alexander Potapenko via gcc
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=20190305230829.GA62096@wildebeest.org \
--to=mark@klomp.org \
--cc=david.brown@hesbynett.no \
--cc=gcc@gcc.gnu.org \
--cc=graham.markall@embecosm.com \
--cc=msebor@gmail.com \
--cc=pj.pandit@yahoo.co.in \
--cc=segher@kernel.crashing.org \
/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).