From: Jan Beulich <jbeulich@suse.com>
To: Binutils <binutils@sourceware.org>
Cc: "H.J. Lu" <hjl.tools@gmail.com>
Subject: [PATCH 0/2] x86: further opcode table line length reduction
Date: Mon, 12 Dec 2022 14:10:45 +0100 [thread overview]
Message-ID: <0d1f3603-35dc-9480-8bf3-2703da96dce5@suse.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 581 bytes --]
Lines are still way too long in many cases, so this series takes
two further steps towards shrinking. While the 1st patch is
hopefully going to be uncontroversial, the 2nd one might be, and
has a respective RFC remark for this very reason. Due to their
size I'm attaching both patches here, and I'll include only
abridged variants (with only some opcode table hunks retained,
just to demonstrate the transformation done, but of course with
all changes to other [non-generated] files retained).
1: change representation of extension opcode
2: omit Cpu prefixes in opcode table
Jan
[-- Attachment #2: binutils-master.tb2 --]
[-- Type: application/octet-stream, Size: 58305 bytes --]
next reply other threads:[~2022-12-12 13:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 13:10 Jan Beulich [this message]
2022-12-12 13:12 ` [PATCH 1/2] x86: change representation of extension opcode Jan Beulich
2022-12-12 13:14 ` [PATCH 2/2] x86: omit Cpu prefixes from opcode table Jan Beulich
2022-12-13 7:29 ` 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=0d1f3603-35dc-9480-8bf3-2703da96dce5@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).