public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/102035] arm/m-profile/cmse add mitigation for CVE-2021-35465 Date: Tue, 24 Aug 2021 13:33:14 +0000 [thread overview] Message-ID: <bug-102035-4-yKAdSPj3RK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102035-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102035 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Richard Earnshaw <rearnsha@gcc.gnu.org>: https://gcc.gnu.org/g:2539763c89a6777502f16457269e2c31d6d95b67 commit r11-8903-g2539763c89a6777502f16457269e2c31d6d95b67 Author: Richard Earnshaw <rearnsha@arm.com> Date: Fri Jun 18 17:16:25 2021 +0100 arm: add erratum mitigation to __gnu_cmse_nonsecure_call [PR102035] Add the recommended erratum mitigation sequence to __gnu_cmse_nonsecure_call for use on Armv8-m.main devices. Since this is in the library code we cannot know in advance whether the core we are running on will be affected by this, so always enable it. libgcc: PR target/102035 * config/arm/cmse_nonsecure_call.S (__gnu_cmse_nonsecure_call): Add vlldm erratum work-around. (cherry picked from commit 574e7950bd6b34e9e2cacce18c802b45505d1d0a)
next prev parent reply other threads:[~2021-08-24 13:33 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-24 10:36 [Bug target/102035] New: " rearnsha at gcc dot gnu.org 2021-08-24 10:37 ` [Bug target/102035] " rearnsha at gcc dot gnu.org 2021-08-24 10:58 ` cvs-commit at gcc dot gnu.org 2021-08-24 10:58 ` cvs-commit at gcc dot gnu.org 2021-08-24 10:58 ` cvs-commit at gcc dot gnu.org 2021-08-24 10:58 ` cvs-commit at gcc dot gnu.org 2021-08-24 13:33 ` cvs-commit at gcc dot gnu.org 2021-08-24 13:33 ` cvs-commit at gcc dot gnu.org [this message] 2021-08-24 13:33 ` cvs-commit at gcc dot gnu.org 2021-08-24 13:33 ` cvs-commit at gcc dot gnu.org 2021-08-24 15:00 ` cvs-commit at gcc dot gnu.org 2021-08-24 15:00 ` cvs-commit at gcc dot gnu.org 2021-08-24 15:00 ` cvs-commit at gcc dot gnu.org 2021-08-24 15:00 ` cvs-commit at gcc dot gnu.org 2021-08-24 15:02 ` rearnsha at gcc dot gnu.org 2021-08-24 16:46 ` rearnsha at gcc dot gnu.org 2021-08-24 16:47 ` rearnsha at gcc dot gnu.org
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=bug-102035-4-yKAdSPj3RK@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).