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/115253] [14/15 regression] New tests added by r14-10122-gad45086178d833 fail on Cortex M23 and M55 bare metal targets Date: Wed, 12 Jun 2024 12:13:23 +0000 [thread overview] Message-ID: <bug-115253-4-O3stSSMknc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115253-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115253 --- Comment #13 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Torbjorn Svensson <azoff@gcc.gnu.org>: https://gcc.gnu.org/g:319081d614dec354ae415472121e0e8ebc4b1402 commit r11-11477-g319081d614dec354ae415472121e0e8ebc4b1402 Author: Torbjörn SVENSSON <torbjorn.svensson@foss.st.com> Date: Thu Jun 6 17:12:11 2024 +0200 arm: Zero/Sign extends for CMSE security on Armv8-M.baseline [PR115253] Properly handle zero and sign extension for Armv8-M.baseline as Cortex-M23 can have the security extension active. Currently, there is an internal compiler error on Cortex-M23 for the epilog processing of sign extension. This patch addresses the following CVE-2024-0151 for Armv8-M.baseline. gcc/ChangeLog: PR target/115253 * config/arm/arm.c (cmse_nonsecure_call_inline_register_clear): Sign extend for Thumb1. (thumb1_expand_prologue): Add zero/sign extend. Signed-off-by: Torbjörn SVENSSON <torbjorn.svensson@foss.st.com> Co-authored-by: Yvan ROUX <yvan.roux@foss.st.com> (cherry picked from commit 65bd0655ece268895e5018e393bafb769e201c78)
next prev parent reply other threads:[~2024-06-12 12:13 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-28 3:42 [Bug target/115253] New: " thiago.bauermann at linaro dot org 2024-05-28 3:46 ` [Bug target/115253] " thiago.bauermann at linaro dot org 2024-05-28 3:47 ` thiago.bauermann at linaro dot org 2024-05-28 3:50 ` thiago.bauermann at linaro dot org 2024-05-28 6:40 ` [Bug target/115253] [14/15 regression] " rguenth at gcc dot gnu.org 2024-06-07 10:17 ` torbjorn.svensson at foss dot st.com 2024-06-07 10:22 ` azoff at gcc dot gnu.org 2024-06-12 8:08 ` cvs-commit at gcc dot gnu.org 2024-06-12 8:08 ` cvs-commit at gcc dot gnu.org 2024-06-12 8:08 ` cvs-commit at gcc dot gnu.org 2024-06-12 8:12 ` cvs-commit at gcc dot gnu.org 2024-06-12 8:12 ` cvs-commit at gcc dot gnu.org 2024-06-12 8:16 ` cvs-commit at gcc dot gnu.org 2024-06-12 8:16 ` cvs-commit at gcc dot gnu.org 2024-06-12 8:17 ` cvs-commit at gcc dot gnu.org 2024-06-12 8:17 ` cvs-commit at gcc dot gnu.org 2024-06-12 12:13 ` cvs-commit at gcc dot gnu.org [this message] 2024-06-12 12:13 ` cvs-commit at gcc dot gnu.org 2024-06-12 12:24 ` azoff at gcc dot gnu.org 2024-06-13 13:34 ` thiago.bauermann at linaro dot 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-115253-4-O3stSSMknc@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).