From: "H.J. Lu" <hjl.tools@gmail.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Richard Biener <rguenther@suse.de>
Subject: Re: [PATCH] INSTALL: Default to --enable-cet=auto
Date: Fri, 27 Nov 2020 10:34:53 -0800 [thread overview]
Message-ID: <CAMe9rOpF6LUEXFp=XMhxYASNFZfARc8mPhirqkjEvRGzZrs1fQ@mail.gmail.com> (raw)
In-Reply-To: <a396d32a-70f1-425-3d8e-d5d14fcc1379@pfeifer.com>
On Fri, Nov 27, 2020 at 8:22 AM Gerald Pfeifer <gerald@pfeifer.com> wrote:
>
> On Fri, 27 Nov 2020, H.J. Lu via Gcc-patches wrote:
> > +@code{--enable-cet=auto} is default. CET is enabled on Linux/x86 if
> > +target binutils supports @code{Intel CET} instructions and disabled
> > +otherwise. In this case, the target libraries are configured to get
> > +additional @option{-fcf-protection} option.
>
> Does that refer to the Linux kernel or GNU/Linux?
>
> THe last sentence does not appear complete. What do you want to say?
>
> "...target libraries are built with @option{-fcf-protection}"?
The new wording is
---
@code{--enable-cet=auto} is default. CET is enabled on Linux/x86 if
target binutils supports @code{Intel CET} instructions and disabled
otherwise. In this case, the target libraries are configured to get
additional @option{-fcf-protection} option.
---
On Linux/x86, if binutils supports CET, target libraries will be compiled
with -fcf-protection}.
> On Fri, 27 Nov 2020, H.J. Lu via Gcc-patches wrote:
> > OK for backport to GCC 10?
>
> Yes, once we have resolved the above.
>
> Gerald
--
H.J.
next prev parent reply other threads:[~2020-11-27 18:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 13:42 H.J. Lu
2020-11-27 14:24 ` Richard Biener
2020-11-27 14:54 ` H.J. Lu
2020-11-27 16:22 ` Gerald Pfeifer
2020-11-27 18:34 ` H.J. Lu [this message]
2023-01-07 22:42 ` Gerald Pfeifer
2020-11-27 19:01 ` Matthias Klose
2020-11-27 19:28 ` H.J. Lu
2020-11-27 20:26 ` Iain Buclaw
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='CAMe9rOpF6LUEXFp=XMhxYASNFZfARc8mPhirqkjEvRGzZrs1fQ@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=rguenther@suse.de \
/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).