public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
* [PATCH 0/3] x86: drop VexSources attribute
@ 2023-02-03  7:43 Jan Beulich
  2023-02-03  7:44 ` [PATCH 1/3] x86: limit use of XOP2SOURCES Jan Beulich
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: Jan Beulich @ 2023-02-03  7:43 UTC (permalink / raw)
  To: Binutils; +Cc: H.J. Lu

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2023-02-03  7:46 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-02-03  7:43 [PATCH 0/3] x86: drop VexSources attribute Jan Beulich
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

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).