public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Binutils <binutils@sourceware.org>, Alan Modra <amodra@gmail.com>
Subject: Re: [PATCH 0/4] x86: follow-on to making disassembler thread-safe
Date: Fri, 10 Jun 2022 12:43:20 -0700	[thread overview]
Message-ID: <CAMe9rOox5JjxtyamVGijSN-x+kAWCtqzy=ZYQukqorrUAtZp2A@mail.gmail.com> (raw)
In-Reply-To: <6fd28ca0-2af4-7335-18d3-31036dea7a4f@suse.com>

On Fri, Jun 10, 2022 at 6:33 AM Jan Beulich <jbeulich@suse.com> wrote:
>
> Alan had noticed ubsan fallout from that combined with my conversion
> of op_riprel to bool[]. In the course of addressing that I did notice
> further things which could do with improving (or so I hope).
>
> 1: properly initialize struct instr_info instance(s)
> 2: shrink prefix related disassembler state fields
> 3: avoid string copy when swapping Vex.W controlled operands
> 4: replace global scratch buffer
>
> Jan

OK for all.

Thanks.

-- 
H.J.

  parent reply	other threads:[~2022-06-10 19:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-10 13:33 Jan Beulich
2022-06-10 13:35 ` [PATCH 1/4] x86: properly initialize struct instr_info instance(s) Jan Beulich
2022-06-10 13:35 ` [PATCH 2/4] x86: shrink prefix related disassembler state fields Jan Beulich
2022-06-10 13:35 ` [PATCH 3/4] x86: avoid string copy when swapping Vex.W controlled operands Jan Beulich
2022-06-10 13:36 ` [PATCH 4/4] x86: replace global scratch buffer Jan Beulich
2022-06-13 13:59   ` H.J. Lu
2022-06-13 14:55     ` Jan Beulich
2022-06-13 20:58       ` H.J. Lu
2022-06-10 19:43 ` H.J. Lu [this message]
2022-06-13  7:54   ` [PATCH 0/4] x86: follow-on to making disassembler thread-safe 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='CAMe9rOox5JjxtyamVGijSN-x+kAWCtqzy=ZYQukqorrUAtZp2A@mail.gmail.com' \
    --to=hjl.tools@gmail.com \
    --cc=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=jbeulich@suse.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).