public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/112470] [11/12/13/14 regression] [AARCH64] stack-protector vulnerability fixing solution impact code size and performance Date: Fri, 10 Nov 2023 22:25:35 +0000 [thread overview] Message-ID: <bug-112470-4-bDE2esceAy@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112470-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112470 Sam James <sjames at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[AARCH64] stack-protector |[11/12/13/14 regression] |vulnerability fixing |[AARCH64] stack-protector |solution impact code size |vulnerability fixing |and performance |solution impact code size | |and performance --- Comment #1 from Sam James <sjames at gcc dot gnu.org> --- This is I suppose a 11/12/13/14 regression (if valid) given we backported it all the way down.
next prev parent reply other threads:[~2023-11-10 22:25 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-10 3:29 [Bug target/112470] New: [AARCH64]stack-protector " dongjianqiang2 at huawei dot com 2023-11-10 22:25 ` sjames at gcc dot gnu.org [this message] 2023-11-10 22:28 ` [Bug target/112470] [11/12/13/14 regression] [AARCH64] stack-protector " pinskia at gcc dot gnu.org 2023-11-13 7:44 ` dongjianqiang2 at huawei dot com 2023-11-13 7:55 ` sjames at gcc dot gnu.org 2023-11-13 9:47 ` rsandifo at gcc dot gnu.org 2023-11-13 10:56 ` dongjianqiang2 at huawei dot com 2023-11-13 11:03 ` rsandifo at gcc dot gnu.org 2023-11-13 12:39 ` dongjianqiang2 at huawei dot com 2023-12-21 19:12 ` pinskia at gcc dot gnu.org 2024-01-25 10:39 ` pinskia at gcc dot gnu.org 2024-01-25 10:39 ` pinskia at gcc dot gnu.org 2024-01-30 12:39 ` xry111 at gcc dot gnu.org 2024-03-19 12:49 ` jakub at gcc dot gnu.org 2024-03-19 13:01 ` xry111 at gcc dot gnu.org 2024-03-25 12:49 ` rguenth 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-112470-4-bDE2esceAy@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).