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/102952] New code-gen options for retpolines and straight line speculation Date: Thu, 18 Nov 2021 16:26:04 +0000 [thread overview] Message-ID: <bug-102952-4-XtCvHKNNLX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102952-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102952 --- Comment #28 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by H.J. Lu <hjl@gcc.gnu.org>: https://gcc.gnu.org/g:2196a681d7810ad8b227bf983f38ba716620545e commit r12-5377-g2196a681d7810ad8b227bf983f38ba716620545e Author: H.J. Lu <hjl.tools@gmail.com> Date: Wed Oct 27 06:27:15 2021 -0700 x86: Add -mindirect-branch-cs-prefix Add -mindirect-branch-cs-prefix to add CS prefix to call and jmp to indirect thunk with branch target in r8-r15 registers so that the call and jmp instruction length is 6 bytes to allow them to be replaced with "lfence; call *%r8-r15" or "lfence; jmp *%r8-r15" at run-time. gcc/ PR target/102952 * config/i386/i386.c (ix86_output_jmp_thunk_or_indirect): Emit CS prefix for -mindirect-branch-cs-prefix. (ix86_output_indirect_branch_via_reg): Likewise. * config/i386/i386.opt: Add -mindirect-branch-cs-prefix. * doc/invoke.texi: Document -mindirect-branch-cs-prefix. gcc/testsuite/ PR target/102952 * gcc.target/i386/indirect-thunk-cs-prefix-1.c: New test. * gcc.target/i386/indirect-thunk-cs-prefix-2.c: Likewise.
next prev parent reply other threads:[~2021-11-18 16:26 UTC|newest] Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-26 15:54 [Bug c/102952] New: " andrew.cooper3 at citrix dot com 2021-10-26 15:56 ` [Bug c/102952] " andrew.cooper3 at citrix dot com 2021-10-26 17:11 ` [Bug target/102952] " andrew.cooper3 at citrix dot com 2021-10-27 7:00 ` rguenth at gcc dot gnu.org 2021-10-27 14:50 ` hjl.tools at gmail dot com 2021-10-27 15:01 ` hjl.tools at gmail dot com 2021-10-27 15:03 ` hjl.tools at gmail dot com 2021-10-27 17:55 ` hjl.tools at gmail dot com 2021-10-27 19:59 ` peterz at infradead dot org 2021-10-27 20:00 ` hjl.tools at gmail dot com 2021-10-27 20:14 ` peterz at infradead dot org 2021-10-27 20:20 ` peterz at infradead dot org 2021-10-27 21:42 ` hjl.tools at gmail dot com 2021-10-27 21:42 ` hjl.tools at gmail dot com 2021-10-27 22:07 ` peterz at infradead dot org 2021-10-27 22:12 ` hjl.tools at gmail dot com 2021-10-27 22:16 ` andrew.cooper3 at citrix dot com 2021-10-27 22:39 ` hjl.tools at gmail dot com 2021-10-27 22:42 ` hjl.tools at gmail dot com 2021-10-27 22:46 ` andrew.cooper3 at citrix dot com 2021-10-27 22:53 ` hjl.tools at gmail dot com 2021-10-28 7:30 ` peterz at infradead dot org 2021-10-28 7:43 ` peterz at infradead dot org 2021-10-28 22:07 ` andrew.cooper3 at citrix dot com 2021-10-28 22:26 ` hjl.tools at gmail dot com 2021-11-15 14:27 ` hjl.tools at gmail dot com 2021-11-16 12:57 ` peterz at infradead dot org 2021-11-16 18:52 ` hjl.tools at gmail dot com 2021-11-17 21:35 ` cvs-commit at gcc dot gnu.org 2021-11-18 16:26 ` cvs-commit at gcc dot gnu.org [this message] 2021-11-18 18:30 ` hjl.tools at gmail dot com 2022-01-06 9:51 ` andrew.cooper3 at citrix dot com 2022-01-06 13:21 ` hjl.tools at gmail dot com 2022-01-06 13:23 ` hjl.tools at gmail dot com 2022-01-06 18:13 ` andrew.cooper3 at citrix dot com 2022-01-06 19:53 ` cvs-commit at gcc dot gnu.org 2022-01-06 20:12 ` hjl.tools at gmail dot com 2022-01-31 8:04 ` rguenth at gcc dot gnu.org 2022-01-31 13:34 ` hjl.tools at gmail dot com 2022-01-31 15:43 ` hjl.tools at gmail dot com 2022-01-31 18:56 ` hjl.tools at gmail dot com 2022-02-07 23:06 ` andrew.cooper3 at citrix dot com 2022-02-16 14:01 ` cvs-commit at gcc dot gnu.org 2022-02-16 14:01 ` cvs-commit at gcc dot gnu.org 2022-02-16 14:01 ` cvs-commit 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-102952-4-XtCvHKNNLX@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).