From: Joseph Myers <joseph@codesourcery.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: <gcc-patches@gcc.gnu.org>, <markus.t.metzger@intel.com>,
<ubizjak@gmail.com>, Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 1/3] Add PTWRITE builtins for x86
Date: Mon, 12 Feb 2018 21:35:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1802122133360.2124@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20180212025317.28068-1-andi@firstfloor.org>
On Sun, 11 Feb 2018, Andi Kleen wrote:
> @@ -27064,6 +27064,9 @@ preferred alignment to @option{-mpreferred-stack-boundary=2}.
> @itemx -mfsgsbase
> @opindex mfsgsbase
> @need 200
> +@itemx -mptwrite
> +@opindex mptwrite
> +@need 200
> @itemx -mrdrnd
> @opindex mrdrnd
> @need 200
This @itemx sequence is above a paragraph that lists the corresponding
instruction set extension for each option. You need to insert an
appropriate entry in that list between "FSGSBASE, RDRND".
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2018-02-12 21:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 2:53 Andi Kleen
2018-02-12 2:53 ` [PATCH 2/3] Add a pass to automatically add ptwrite instrumentation Andi Kleen
2018-02-12 2:53 ` [PATCH 3/3] Add tests for the vartrace pass Andi Kleen
2018-02-12 21:35 ` Joseph Myers [this message]
2018-05-09 11:29 ` [PATCH 1/3] Add PTWRITE builtins for x86 Peryt, Sebastian
2018-05-09 12:11 ` Uros Bizjak
2018-05-11 1:57 ` Andi Kleen
2018-05-11 6:31 ` Uros Bizjak
2018-11-04 6:33 Andi Kleen
2018-11-08 17:10 ` Andi Kleen
2018-11-08 17:30 Uros Bizjak
2018-11-08 18:03 ` Andi Kleen
2018-11-08 18:11 ` Uros Bizjak
2018-11-10 2:54 ` Segher Boessenkool
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=alpine.DEB.2.20.1802122133360.2124@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=markus.t.metzger@intel.com \
--cc=ubizjak@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).