From: Jan Beulich <jbeulich@suse.com>
To: Binutils <binutils@sourceware.org>
Cc: "H.J. Lu" <hjl.tools@gmail.com>
Subject: [PATCH 0/3] x86: assorted opcode processing adjustments
Date: Fri, 3 Feb 2023 08:30:32 +0100 [thread overview]
Message-ID: <1387362a-7920-de18-18e5-9fe42f923f0b@suse.com> (raw)
The first change follows what was already done for Intel syntax code.
The second is finally doing what I was meaning to do for quite some
time, noticing the inefficiencies once again while preparing patch 1.
The third change is perhaps just a first step towards re-arranging
how we represent template attributes; see there for possible further
steps.
1: improve special casing of certain insns
2: simplify a few expressions
3: move (and rename) opcodespace attribute
Jan
next reply other threads:[~2023-02-03 7:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 7:30 Jan Beulich [this message]
2023-02-03 7:32 ` [PATCH 1/3] x86: improve special casing of certain insns Jan Beulich
2023-02-03 7:32 ` [PATCH 2/3] x86: simplify a few expressions Jan Beulich
2023-02-03 7:33 ` [PATCH 3/3] x86: move (and rename) opcodespace attribute 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=1387362a-7920-de18-18e5-9fe42f923f0b@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).