public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/93654] Inappropriate "-fcf-protection and -mindirect-branch=thunk are incompatible on x86_64" restriction Date: Tue, 28 Apr 2020 15:02:26 +0000 [thread overview] Message-ID: <bug-93654-4-aYfWM2nCRZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-93654-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93654 --- Comment #3 from H.J. Lu <hjl.tools at gmail dot com> --- Please DO disable -fcf-protection in the kernel build. We are enabling CET for the user space first. The kernel CET will be the next. I am enclosing a proposal to make -fcf-protection compatible with retpoline. It targets user space. It can be made compatible with kernel.
next prev parent reply other threads:[~2020-04-28 15:02 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-93654-4@http.gcc.gnu.org/bugzilla/> 2020-03-16 18:02 ` dwmw2 at infradead dot org 2020-04-28 15:01 ` hjl.tools at gmail dot com 2020-04-28 15:02 ` hjl.tools at gmail dot com [this message] 2020-04-28 22:52 ` hjl.tools at gmail dot com 2020-04-28 23:14 ` andrew.cooper3 at citrix dot com 2020-04-29 0:12 ` hjl.tools at gmail dot com 2020-04-29 0:17 ` andrew.cooper3 at citrix dot com 2020-04-29 2:00 ` hjl.tools at gmail dot com 2020-04-29 12:00 ` cvs-commit at gcc dot gnu.org 2020-04-29 12:12 ` cvs-commit at gcc dot gnu.org 2020-04-29 12:18 ` andrew.cooper3 at citrix dot com 2020-04-29 12:22 ` [Bug target/93654] [9/10 Regression] Inappropriate "-fcf-protection and -mindirect-branch=thunk-extern are incompatible" restriction hjl.tools at gmail dot com
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-93654-4-aYfWM2nCRZ@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).