From: Uros Bizjak <ubizjak@gmail.com>
To: "Tsimbalist, Igor V" <igor.v.tsimbalist@intel.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: 0005-Part-5.-Add-x86-CET-documentation
Date: Wed, 20 Sep 2017 14:13:00 -0000 [thread overview]
Message-ID: <CAFULd4YEx_dP3wfMqf2KDEZEkKVxRagcpPujnue2EMaQ-oQGvw@mail.gmail.com> (raw)
In-Reply-To: <D511F25789BA7F4EBA64C8A63891A0028ADB678D@irsmsx105.ger.corp.intel.com>
On Wed, Sep 20, 2017 at 11:20 AM, Tsimbalist, Igor V
<igor.v.tsimbalist@intel.com> wrote:
> Uros, could you please review this patch as it's a part of x86 specific changes you have reviewed already.
Please proofread and spell-check the text. There are grammatical errors, e.g.:
+When compiled with the @option{-finstrument-control-flow} option
+the ENDBR instruction also inserted at addresses to which indirect
and typos, such as:
+control-flow trasfer can happen.
English is not my tongue, but these two popped out immediately.
Other than that,
-a program security by checking a target address of control-flow
+a program security by checking target addresses of control-flow
Spurious change.
+@option{mshstk} options. Each of these options enables coresponding
Missing dash, and a typo.
+This option instructs the compiler to use only indirect branch tracking
+(indirect calls and jumps) support from x86 Control-flow Enforcment
Typo.
+Technology (CET) implementation, see also @code{-mcet} option. The
+option has effect only if @code{-finstrument-control-flow} option is
+specified. The option @code{-mibt} is on by default when @code{-mcet}
+option is specified.
Please use @option{} for options.
+This option instructs compiler to use only shadow stack (return address
+tracking) support from x86 Control-flow Enforcment Technology (CET)
+implementation, see also @code{-mcet} option. The option has effect
+only if @code{-finstrument-control-flow} option is specified. The
+option @code{-mshstk} is on by default when @code{-mcet} option is
+specified.
Also in the above text.
Uros.
next prev parent reply other threads:[~2017-09-20 14:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 8:57 0005-Part-5.-Add-x86-CET-documentation Tsimbalist, Igor V
2017-09-20 9:21 ` 0005-Part-5.-Add-x86-CET-documentation Tsimbalist, Igor V
2017-09-20 14:13 ` Uros Bizjak [this message]
2017-09-25 3:43 ` 0005-Part-5.-Add-x86-CET-documentation Sandra Loosemore
2017-09-26 13:47 ` 0005-Part-5.-Add-x86-CET-documentation Tsimbalist, Igor V
2017-09-27 3:40 ` 0005-Part-5.-Add-x86-CET-documentation Sandra Loosemore
2017-09-27 8:52 ` 0005-Part-5.-Add-x86-CET-documentation Florian Weimer
2017-09-27 11:52 ` 0005-Part-5.-Add-x86-CET-documentation Tsimbalist, Igor V
2017-09-27 16:48 ` 0005-Part-5.-Add-x86-CET-documentation Sandra Loosemore
2017-09-27 17:01 ` 0005-Part-5.-Add-x86-CET-documentation Joseph Myers
2017-09-28 23:29 ` 0005-Part-5.-Add-x86-CET-documentation Jeff Law
2017-09-27 15:17 ` 0005-Part-5.-Add-x86-CET-documentation Tsimbalist, Igor V
2017-09-28 23:32 ` 0005-Part-5.-Add-x86-CET-documentation Jeff Law
2017-09-29 5:15 ` 0005-Part-5.-Add-x86-CET-documentation Sandra Loosemore
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=CAFULd4YEx_dP3wfMqf2KDEZEkKVxRagcpPujnue2EMaQ-oQGvw@mail.gmail.com \
--to=ubizjak@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=igor.v.tsimbalist@intel.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).