From: "H.J. Lu" <hjl.tools@gmail.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: [PATCH] x86: generalize gas documentation for disabling of ISA extensions
Date: Mon, 17 Oct 2022 15:28:17 -0700 [thread overview]
Message-ID: <CAMe9rOqQahvPA9Ho=JYZ8nUZFLDLWFbxn7KyYa+0_fyfMy0iog@mail.gmail.com> (raw)
In-Reply-To: <85dd526c-d3a7-72dc-5444-ed5573eebec1@suse.com>
On Mon, Oct 17, 2022 at 1:30 AM Jan Beulich <jbeulich@suse.com> wrote:
>
> As of commit ae89daecb132 ("x86: generalize disabling of sub-
> architectures") there's no arbitrary subset of ISAs which can also be
> disabled. This should have been reflected in documentation right away.
> Since I failed to do so, correct this now.
>
> --- a/gas/doc/c-i386.texi
> +++ b/gas/doc/c-i386.texi
> @@ -137,16 +137,9 @@ accept various extension mnemonics. For
> @code{287},
> @code{387},
> @code{687},
> -@code{no87},
> -@code{no287},
> -@code{no387},
> -@code{no687},
> @code{cmov},
> -@code{nocmov},
> @code{fxsr},
> -@code{nofxsr},
> @code{mmx},
> -@code{nommx},
> @code{sse},
> @code{sse2},
> @code{sse3},
> @@ -155,18 +148,8 @@ accept various extension mnemonics. For
> @code{sse4.1},
> @code{sse4.2},
> @code{sse4},
> -@code{nosse},
> -@code{nosse2},
> -@code{nosse3},
> -@code{nosse4a},
> -@code{nossse3},
> -@code{nosse4.1},
> -@code{nosse4.2},
> -@code{nosse4},
> @code{avx},
> @code{avx2},
> -@code{noavx},
> -@code{noavx2},
> @code{adx},
> @code{rdseed},
> @code{prfchw},
> @@ -189,9 +172,7 @@ accept various extension mnemonics. For
> @code{serialize},
> @code{tsxldtrk},
> @code{kl},
> -@code{nokl},
> @code{widekl},
> -@code{nowidekl},
> @code{hreset},
> @code{avx512f},
> @code{avx512cd},
> @@ -213,37 +194,9 @@ accept various extension mnemonics. For
> @code{avx512_bf16},
> @code{avx_vnni},
> @code{avx512_fp16},
> -@code{noavx512f},
> -@code{noavx512cd},
> -@code{noavx512er},
> -@code{noavx512pf},
> -@code{noavx512vl},
> -@code{noavx512bw},
> -@code{noavx512dq},
> -@code{noavx512ifma},
> -@code{noavx512vbmi},
> -@code{noavx512_4fmaps},
> -@code{noavx512_4vnniw},
> -@code{noavx512_vpopcntdq},
> -@code{noavx512_vbmi2},
> -@code{noavx512_vnni},
> -@code{noavx512_bitalg},
> -@code{noavx512_vp2intersect},
> -@code{notdx},
> -@code{noavx512_bf16},
> -@code{noavx_vnni},
> -@code{noavx512_fp16},
> -@code{noenqcmd},
> -@code{noserialize},
> -@code{notsxldtrk},
> @code{amx_int8},
> -@code{noamx_int8},
> @code{amx_bf16},
> -@code{noamx_bf16},
> @code{amx_tile},
> -@code{noamx_tile},
> -@code{nouintr},
> -@code{nohreset},
> @code{vmx},
> @code{vmfunc},
> @code{smx},
> @@ -291,8 +244,8 @@ accept various extension mnemonics. For
> @code{tlbsync},
> @code{svme} and
> @code{padlock}.
> -Note that rather than extending a basic instruction set, the extension
> -mnemonics starting with @code{no} revoke the respective functionality.
> +Note that these extension mnemonics can be prefixed with @code{no} to revoke
> +the respective (and any dependent) functionality.
>
> When the @code{.arch} directive is used with @option{-march}, the
> @code{.arch} directive will take precedent.
> @@ -1559,6 +1512,9 @@ conditional jumps will be promoted when
> sequence consisting of a conditional jump of the opposite sense around
> an unconditional jump to the target.
>
> +Note that the sub-architecture specifiers (starting with a dot) can be prefixed
> +with @code{no} to revoke the respective (and any dependent) functionality.
> +
> Following the CPU architecture (but not a sub-architecture, which are those
> starting with a dot), you may specify @samp{jumps} or @samp{nojumps} to
> control automatic promotion of conditional jumps. @samp{jumps} is the
OK.
Thanks.
--
H.J.
prev parent reply other threads:[~2022-10-17 22:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 8:30 Jan Beulich
2022-10-17 22:28 ` H.J. Lu [this message]
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='CAMe9rOqQahvPA9Ho=JYZ8nUZFLDLWFbxn7KyYa+0_fyfMy0iog@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.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).