From: Jan Beulich <jbeulich@suse.com>
To: Binutils <binutils@sourceware.org>
Cc: "H.J. Lu" <hjl.tools@gmail.com>
Subject: [PATCH 0/3] x86: drop VexSources attribute
Date: Fri, 3 Feb 2023 08:43:08 +0100 [thread overview]
Message-ID: <aad64ab4-440b-7f00-c64e-50f8fe215c18@suse.com> (raw)
This attribute's existence has been bothering me for years; I merely never
dared to touch it because the hackery looked pretty fragile. In the course
of trying to get .insn to work sensibly (and without overly intrusive
changes to the assembler), I finally had to properly understand what the
special case code does. And voila - XOP2SOURCES is fully redundant with
other (in part special case) handling we have, while VEX3SOURCES uses can
easily be expressed differently.
1: limit use of XOP2SOURCES
2: drop use of XOP2SOURCES
3: drop use of VEX3SOURCES
While I don't think there are any conflicts (except in generated files),
if in doubt this is assumed to go on top of "x86: assorted opcode
processing adjustments".
Jan
next reply other threads:[~2023-02-03 7:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 7:43 Jan Beulich [this message]
2023-02-03 7:44 ` [PATCH 1/3] x86: limit use of XOP2SOURCES Jan Beulich
2023-02-03 7:45 ` [PATCH 2/3] x86: drop " Jan Beulich
2023-02-03 7:46 ` [PATCH 3/3] x86: drop use of VEX3SOURCES Jan Beulich
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=aad64ab4-440b-7f00-c64e-50f8fe215c18@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.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).