From: Matthew Malcomson <matthew.malcomson@arm.com>
To: gcc-patches@gcc.gnu.org
Cc: Richard.Earnshaw@arm.com, Kyrylo.Tkachov@arm.com,
Ross Burton <Ross.Burton@arm.com>
Subject: SLS Mitigation patches backported for GCC9
Date: Tue, 21 Jul 2020 16:15:34 +0100 [thread overview]
Message-ID: <159534453451.25601.18119761260522884038.scripted-patch-series@arm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 481 bytes --]
Hello,
Eventually we will want to backport the SLS patches to older branches.
When the GCC10 release is unfrozen we will work on getting the same patches
already posted backported to that branch. The patches already posted on the
mailing list apply cleanly to the current releases/gcc-10 branch.
I've heard interest in having the GCC 9 patches, so I'm posting the modified
versions upstream sooner than otherwise.
Cheers,
Matthew
Entire patch series attached to cover letter.
[-- Attachment #2: all-patches.tar.gz --]
[-- Type: application/gzip, Size: 12349 bytes --]
next reply other threads:[~2020-07-21 15:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 15:15 Matthew Malcomson [this message]
2020-07-21 15:15 ` aarch64: (GCC-9 Backport) New Straight Line Speculation (SLS) mitigation flags Matthew Malcomson
2020-07-21 15:15 ` aarch64: (GCC-9 Backport) Mitigate SLS for BLR instruction Matthew Malcomson
2020-07-21 15:15 ` aarch64: (GCC-9 Backport) Introduce SLS mitigation for RET and BR instructions Matthew Malcomson
2020-07-24 11:01 ` SLS Mitigation patches backported for GCC9 Kyrylo Tkachov
2020-07-24 16:02 ` Matthew Malcomson
2020-08-04 8:33 ` Kyrylo Tkachov
2020-11-12 18:34 ` Sebastian Pop
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=159534453451.25601.18119761260522884038.scripted-patch-series@arm.com \
--to=matthew.malcomson@arm.com \
--cc=Kyrylo.Tkachov@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=Ross.Burton@arm.com \
--cc=gcc-patches@gcc.gnu.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).