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 v4 0/8] x86: suffix handling changes
Date: Thu, 13 Oct 2022 10:15:06 +0200	[thread overview]
Message-ID: <4aa2665c-535f-da2d-1edb-4eb1f4195c3e@suse.com> (raw)

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

1: constify parse_insn()'s input
2: introduce Pass2 insn attribute
3: re-work insn/suffix recognition
4: further re-work insn/suffix recognition to also cover MOVSL
5: don't recognize/derive Q suffix in the common case
6: allow HLE store of accumulator to absolute 32-bit address
7: move bad-use-of-TLS-reloc check
8: drop (now) stray IsString

Note that patches 5...7 were previously approved, but can't be committed
ahead of the earlier ones.

Jan

             reply	other threads:[~2022-10-13  8:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-13  8:15 Jan Beulich [this message]
2022-10-13  8:16 ` [PATCH v4 1/8] x86: constify parse_insn()'s input Jan Beulich
2022-10-13  8:17 ` [PATCH v4 2/8] x86: introduce Pass2 insn attribute Jan Beulich
2022-10-13  8:18 ` [PATCH v4 3/8] x86: re-work insn/suffix recognition Jan Beulich
2022-10-13  8:18 ` [PATCH v4 4/8] x86-64: further re-work insn/suffix recognition to also cover MOVSL Jan Beulich
2022-10-13  8:19 ` [PATCH v4 5/8] ix86: don't recognize/derive Q suffix in the common case Jan Beulich
2022-10-13  8:20 ` [PATCH v4 6/8] x86-64: allow HLE store of accumulator to absolute 32-bit address Jan Beulich
2022-10-13  8:21 ` [PATCH v4 7/8] x86: move bad-use-of-TLS-reloc check Jan Beulich
2022-10-13  8:22 ` [PATCH v4 8/8] x86: drop (now) stray IsString 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=4aa2665c-535f-da2d-1edb-4eb1f4195c3e@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).