From: Jan Beulich <jbeulich@suse.com>
To: Binutils <binutils@sourceware.org>
Cc: "H.J. Lu" <hjl.tools@gmail.com>
Subject: [PATCH v6 0/7] x86: suffix handling changes
Date: Fri, 4 Nov 2022 11:49:26 +0100 [thread overview]
Message-ID: <6d71dc80-91c8-7bc8-c57f-4f771ca59fab@suse.com> (raw)
... accompanied by a few other improvements (or so I hope) found
along the way.
The only change in v6 is the dropping of the new Pass2 attribute, with
appropriate adjustments throughout the series.
1: constify parse_insn()'s input
2: re-work insn/suffix recognition
3: don't recognize/derive Q suffix in the common case
4: allow HLE store of accumulator to absolute 32-bit address
5: move bad-use-of-TLS-reloc check
6: drop (now) stray IsString
7: further re-work insn/suffix recognition to also cover MOVSX
Note that patches 3...5 were previously approved (albeit 3 has now
changed because of the re-ordering of the series in v5), but can't be
committed ahead of the earlier ones.
Jan
next reply other threads:[~2022-11-04 10:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 10:49 Jan Beulich [this message]
2022-11-04 10:50 ` [PATCH v6 1/7] x86: constify parse_insn()'s input Jan Beulich
2022-11-04 10:51 ` [PATCH v6 2/7] x86: re-work insn/suffix recognition Jan Beulich
2022-11-04 23:54 ` H.J. Lu
2022-11-07 10:23 ` Jan Beulich
2022-11-08 1:21 ` H.J. Lu
2022-11-08 8:29 ` Jan Beulich
2022-11-04 10:52 ` [PATCH v6 3/7] ix86: don't recognize/derive Q suffix in the common case Jan Beulich
2022-11-04 10:52 ` [PATCH v6 4/7] x86-64: allow HLE store of accumulator to absolute 32-bit address Jan Beulich
2022-11-04 10:53 ` [PATCH v6 5/7] x86: move bad-use-of-TLS-reloc check Jan Beulich
2022-11-04 10:53 ` [PATCH v6 6/7] x86: drop (now) stray IsString Jan Beulich
2022-11-04 10:54 ` [PATCH v6 7/7] x86: further re-work insn/suffix recognition to also cover MOVSX 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=6d71dc80-91c8-7bc8-c57f-4f771ca59fab@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).