public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
* [PATCH 0/4] x86: follow-on to making disassembler thread-safe
@ 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
                   ` (4 more replies)
  0 siblings, 5 replies; 10+ messages in thread
From: Jan Beulich @ 2022-06-10 13:33 UTC (permalink / raw)
  To: Binutils

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

^ permalink raw reply	[flat|nested] 10+ messages in thread

end of thread, other threads:[~2022-06-13 20:59 UTC | newest]

Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-06-10 13:33 [PATCH 0/4] x86: follow-on to making disassembler thread-safe 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 ` [PATCH 0/4] x86: follow-on to making disassembler thread-safe H.J. Lu
2022-06-13  7:54   ` Jan Beulich

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).