public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	Florian Weimer <fweimer@redhat.com>
Subject: Re: [PATCH v2] x86: Document -mcet-switch
Date: Thu, 19 May 2022 08:02:03 +0200	[thread overview]
Message-ID: <CAFiYyc2mZ-i2dMqNxVjvPL8kB4Y8=C+U0nxZ8Wcr6BFnQrTrZQ@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOqR3P5AsC3ZSgEQcT68bR-dVmHcfVi0DT-AbEok3-yLsw@mail.gmail.com>

On Wed, May 18, 2022 at 7:32 PM H.J. Lu via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
>
> On Wed, May 11, 2022 at 1:52 PM H.J. Lu <hjl.tools@gmail.com> wrote:
> >
> > When -fcf-protection=branch is used, the compiler will generate jump
> > tables for switch statements where the indirect jump is prefixed with
> > the NOTRACK prefix, so it can jump to non-ENDBR targets.  Since the
> > indirect jump targets are generated by the compiler, they are always
> > valid.
> >
> > Document -mcet-switch to generate jump tables for switch statements with
> > ENDBR and skip the NOTRACK prefix for indirect jump.  This option should
> > be used when the NOTRACK prefix is disabled.
> >
> >         PR target/104816
> >         * config/i386/i386.opt: Remove Undocumented.
> >         * doc/invoke.texi: Document -mcet-switch.
> > ---
> >  gcc/config/i386/i386.opt | 2 +-
> >  gcc/doc/invoke.texi      | 8 +++++++-
> >  2 files changed, 8 insertions(+), 2 deletions(-)
> >
> > diff --git a/gcc/config/i386/i386.opt b/gcc/config/i386/i386.opt
> > index a6b0e28f238..0dbaacb57ed 100644
> > --- a/gcc/config/i386/i386.opt
> > +++ b/gcc/config/i386/i386.opt
> > @@ -1047,7 +1047,7 @@ Enable shadow stack built-in functions from Control-flow Enforcement
> >  Technology (CET).
> >
> >  mcet-switch
> > -Target Undocumented Var(flag_cet_switch) Init(0)
> > +Target Var(flag_cet_switch) Init(0)
> >  Turn on CET instrumentation for switch statements that use a jump table and
> >  an indirect jump.
> >
> > diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
> > index 7a35d9613a4..968853690f9 100644
> > --- a/gcc/doc/invoke.texi
> > +++ b/gcc/doc/invoke.texi
> > @@ -1420,7 +1420,8 @@ See RS/6000 and PowerPC Options.
> >  -msse4a  -m3dnow  -m3dnowa  -mpopcnt  -mabm  -mbmi  -mtbm  -mfma4  -mxop @gol
> >  -madx  -mlzcnt  -mbmi2  -mfxsr  -mxsave  -mxsaveopt  -mrtm  -mhle  -mlwp @gol
> >  -mmwaitx  -mclzero  -mpku  -mthreads  -mgfni  -mvaes  -mwaitpkg @gol
> > --mshstk -mmanual-endbr -mforce-indirect-call  -mavx512vbmi2 -mavx512bf16 -menqcmd @gol
> > +-mshstk -mmanual-endbr -mcet-switch -mforce-indirect-call @gol
> > +-mavx512vbmi2 -mavx512bf16 -menqcmd @gol
> >  -mvpclmulqdq  -mavx512bitalg  -mmovdiri  -mmovdir64b  -mavx512vpopcntdq @gol
> >  -mavx5124fmaps  -mavx512vnni  -mavx5124vnniw  -mprfchw  -mrdpid @gol
> >  -mrdseed  -msgx -mavx512vp2intersect -mserialize -mtsxldtrk@gol
> > @@ -32641,6 +32642,11 @@ function attribute. This is useful when used with the option
> >  @option{-fcf-protection=branch} to control ENDBR insertion at the
> >  function entry.
> >
> > +@item -mcet-switch
> > +@opindex mcet-switch
> > +Turn on CET instrumentation for switch statements that use a jump table
> > +and an indirect jump.
> > +

Can you explain the difference between -mcet-switch and -mno-cet-switch here
please and indicate the default?  The above doesn't sound useful to me.

> >  @item -mcall-ms2sysv-xlogues
> >  @opindex mcall-ms2sysv-xlogues
> >  @opindex mno-call-ms2sysv-xlogues
> > --
> > 2.35.1
> >
>
> Any comments?
>
> Thanks.
>
> --
> H.J.

  reply	other threads:[~2022-05-19  6:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-11 20:52 H.J. Lu
2022-05-18 17:27 ` H.J. Lu
2022-05-19  6:02   ` Richard Biener [this message]
2022-05-19 20:37     ` H.J. Lu
2022-05-19 20:49       ` Florian Weimer
2022-05-19 23:37         ` 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='CAFiYyc2mZ-i2dMqNxVjvPL8kB4Y8=C+U0nxZ8Wcr6BFnQrTrZQ@mail.gmail.com' \
    --to=richard.guenther@gmail.com \
    --cc=fweimer@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hjl.tools@gmail.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).