From: Segher Boessenkool <segher@kernel.crashing.org>
To: Jeff Law <law@redhat.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH][RFA/RFC] Stack clash mitigation patch 05/08
Date: Thu, 20 Jul 2017 13:14:00 -0000 [thread overview]
Message-ID: <20170720130927.GZ13471@gate.crashing.org> (raw)
In-Reply-To: <91c49a05-cb65-a850-a653-d181749075dc@redhat.com>
Hi Jeff,
On Tue, Jul 18, 2017 at 11:17:48PM -0600, Jeff Law wrote:
> It turns out combine-stack-adjustments would take
>
> allocate PROBE_INTERVAL
> probe
> allocate PROBE_INTERVAL
> probe
> allocate PROBE_INTERVAL
> probe
> allocate RESIDUAL
>
> And turn that into
>
> allocate (3 * PROBE_INTERVAL) + residual
> probe
> probe
> probe
>
> Adjusting the address of the probes appropriately. Ugh.
>
> This patch introduces a new note that the backend can attach to a stack
> adjustment which essentially tells c-s-a to not merge it into other
> adjustments. THere's an x86 specific test to verify behavior.
Can only combine-stack-adjustments do this? It seems like something
many passes could do, and then your new note doesn't help.
Segher
next prev parent reply other threads:[~2017-07-20 13:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 5:17 Jeff Law
2017-07-20 13:14 ` Segher Boessenkool [this message]
2017-07-20 14:20 ` Jeff Law
2017-07-21 20:25 ` Segher Boessenkool
2017-07-31 15:53 ` Jeff Law
-- strict thread matches above, loose matches on Subject: below --
2017-07-11 21:21 Jeff Law
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=20170720130927.GZ13471@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.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).