public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Binutils <binutils@sourceware.org>
Cc: "H.J. Lu" <hjl.tools@gmail.com>
Subject: [PATCH v7 0/7] x86: suffix handling changes
Date: Fri, 2 Dec 2022 11:13:42 +0100	[thread overview]
Message-ID: <dc39887b-fc6e-2827-e0b1-e99949e08796@suse.com> (raw)

... accompanied by a few other improvements (or so I hope) found
along the way.

Apart from re-basing this is merely a re-submission, in an attempt to
revive the discussion: There are multiple bugs being fixed by this
series, which I'd like to ask to not put off simply with a subjective
qualification of them being minor. Plus even if minor, it's one thing
to not invest time into addressing a minor bug, but here a fix is
being supplied, ready for committing. I'd like to also stress again
that I've taken quite a bit of time to address concerns, and to hence
find a viable compromise.

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.

While I don't think there's any collision with the also pending "x86:
break gas dependency on libopcodes" series (apart from generated files),
just in case: The series here is presented on top of that one, but could
be easily re-based ahead.

Jan

             reply	other threads:[~2022-12-02 10:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-02 10:13 Jan Beulich [this message]
2022-12-02 10:18 ` [PATCH v7 1/7] x86: constify parse_insn()'s input Jan Beulich
2022-12-02 10:18 ` [PATCH v7 2/7] x86: re-work insn/suffix recognition Jan Beulich
2022-12-02 10:19 ` [PATCH v7 3/7] ix86: don't recognize/derive Q suffix in the common case Jan Beulich
2022-12-02 10:20 ` [PATCH v7 4/7] x86-64: allow HLE store of accumulator to absolute 32-bit address Jan Beulich
2022-12-02 10:20 ` [PATCH v7 5/7] x86: move bad-use-of-TLS-reloc check Jan Beulich
2022-12-02 10:21 ` [PATCH v7 6/7] x86: drop (now) stray IsString Jan Beulich
2022-12-02 10:21 ` [PATCH v7 7/7] x86: further re-work insn/suffix recognition to also cover MOVSX Jan Beulich
2022-12-09 10:56 ` [PATCH v7 0/7] x86: suffix handling changes 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=dc39887b-fc6e-2827-e0b1-e99949e08796@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).