From: Jeff Law <jeffreyalaw@gmail.com>
To: Florian Weimer <fweimer@redhat.com>,
Jeff Law via Libc-alpha <libc-alpha@sourceware.org>
Cc: Joe Simmons-Talbott <josimmon@redhat.com>
Subject: Re: [PATCH v3] ifaddrs: Get rid of alloca
Date: Thu, 1 Jun 2023 09:13:06 -0600 [thread overview]
Message-ID: <e465ee5e-bbf4-80af-c6bd-6000ae473211@gmail.com> (raw)
In-Reply-To: <87ilc7rzn3.fsf@oldenburg.str.redhat.com>
On 6/1/23 09:05, Florian Weimer wrote:
> * Jeff Law via Libc-alpha:
>
>> Instead I wanted to have GCC prove particular allocations were safe to
>> transform into alloca. That never panned out, but I still think the
>> compiler is the right place to exploit the performance improvements
>> one gets from alloca vs malloc/free.
>
> We got -fstack-clash-protection, which is I think is good enough from a
> security point of view.
Yea... Though I still want to dispose of explicitly using alloca :-)
Interestingly enough I'm likey to have to spin up stack-clash-protection
within the next few months for RISC-V. Though I may look to delegate
it -- it'd be a great learning project for one of my compiler engineers.
jeff
prev parent reply other threads:[~2023-06-01 15:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 15:25 Joe Simmons-Talbott
2023-05-31 12:24 ` Adhemerval Zanella Netto
2023-06-01 14:43 ` Jeff Law
2023-06-01 15:05 ` Florian Weimer
2023-06-01 15:13 ` Jeff Law [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=e465ee5e-bbf4-80af-c6bd-6000ae473211@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=fweimer@redhat.com \
--cc=josimmon@redhat.com \
--cc=libc-alpha@sourceware.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).