From: "H.J. Lu" <hjl.tools@gmail.com>
To: gcc-patches@gcc.gnu.org
Cc: Jakub Jelinek <jakub@redhat.com>
Subject: [PATCH 0/2] GCC_CET_HOST_FLAGS: Check if host supports multi-byte NOPs
Date: Tue, 23 Mar 2021 15:39:04 -0700 [thread overview]
Message-ID: <20210323223906.7985-1-hjl.tools@gmail.com> (raw)
Check if host supports multi-byte NOPs before enabling CET on host.
This fixes:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99703
H.J. Lu (2):
GCC_CET_HOST_FLAGS: Check if host supports multi-byte NOPs
GCC_CET_HOST_FLAGS: Check if host supports multi-byte NOPs
config/cet.m4 | 19 +++++++++++--
gcc/configure | 45 +++++++++++++++++++++---------
libbacktrace/configure | 29 +++++++++++++++++++
libcc1/configure | 45 +++++++++++++++++++++---------
libcpp/configure | 29 +++++++++++++++++++
libdecnumber/configure | 29 +++++++++++++++++++
libiberty/configure | 29 +++++++++++++++++++
lto-plugin/configure | 63 +++++++++++++++++++++++++++++++-----------
8 files changed, 243 insertions(+), 45 deletions(-)
--
2.30.2
next reply other threads:[~2021-03-23 22:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 22:39 H.J. Lu [this message]
2021-03-23 22:39 ` [PATCH 1/2] " H.J. Lu
2021-05-02 13:27 ` PING^1 " H.J. Lu
2021-05-03 8:23 ` Richard Biener
2021-03-23 22:39 ` [PATCH 2/2] " H.J. Lu
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=20210323223906.7985-1-hjl.tools@gmail.com \
--to=hjl.tools@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
/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: link
Be 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).