archive mirror
 help / color / mirror / Atom feed
From: Dan Li <>
Subject: Re: [PATCH] [PATCH,v4,1/1,AARCH64][PR102768] aarch64: Add compiler support for Shadow Call Stack
Date: Sat, 12 Feb 2022 00:43:18 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 2/11/22 07:35, Richard Sandiford wrote:
> Dan Li <> writes:
>> On 2/11/22 01:53, Richard Sandiford wrote:
>>> Dan Li <> writes:
>>>> On 2/10/22 01:55, Richard Sandiford wrote:
>> And I think maybe we could handle this through three patches:
>> 1.Keep current patch (a V5) unchanged for scs.
>> 2.Add shrink-warpping for X30:
>> logically this might be a separate topic, and I think more testing
>> might be needed here (Well, I'm a little worried about if there might
>> be other effects, since I just read this part of the code roughly
>> yesterday).
>> 3.Add scs push/pop to shrink-wrapping (and maybe we can do the same for
>> the PAC code in pro/epilogue, since it's also the operation of the X30).
> Yeah, that's fair.
> (Like I said earlier, I wasn't asking for the shrink-wrapping change.
> It was just a note in passing.  But as you point out, the individual
> shrink-wrapping support would be even more work than I'd imagined.)

Hi, Richard,
I have sent out the v5[1] and rebased it to mainline at the same time,
please let me know if there is anything else I need to do :)



      parent reply	other threads:[~2022-02-12  8:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-05 11:04 [PATCH] [PATCH,v4,1/1,AARCH64][PR102768] aarch64: Add compiler support for Shadow Call Stack Dan Li
2022-02-09 16:08 ` Richard Sandiford
2022-02-10  3:06   ` Dan Li
2022-02-10  9:55     ` Richard Sandiford
2022-02-11  8:57       ` Dan Li
2022-02-11  9:53         ` Richard Sandiford
2022-02-11 13:43           ` Dan Li
2022-02-11 15:35             ` Richard Sandiford
2022-02-12  5:30               ` Dan Li
2022-02-12  8:43               ` Dan Li [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \

* 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 NNTP newsgroup(s).