From: Richard Henderson <richard.henderson@linaro.org>
To: qemu-devel@nongnu.org
Cc: balaton@eik.bme.hu, philmd@linaro.org, sw@weilnetz.de
Subject: [PATCH v2 0/6] Two -Wclobbered fixes, plus other cleanup
Date: Mon, 7 Nov 2022 08:28:46 +1100 [thread overview]
Message-ID: <20221106212852.152384-1-richard.henderson@linaro.org> (raw)
Stefan reported for accel/tcg, and I reproduced on Ubuntu 22.04.
Changes for v2:
* Incorporate suggested changes to nanomips.c (phil, balaton).
r~
Richard Henderson (6):
disas/nanomips: Move setjmp into nanomips_dis
disas/nanomips: Merge insn{1,2,3} into words[3]
disas/nanomips: Split out read_u16
disas/nanomips: Tidy read for 48-bit opcodes
tcg: Move TCG_TARGET_HAS_direct_jump init to tb_gen_code
accel/tcg: Split out setjmp_gen_code
accel/tcg/translate-all.c | 68 ++++++++++++-----------
disas/nanomips.c | 110 ++++++++++++++++----------------------
tcg/tcg.c | 12 +++++
3 files changed, 90 insertions(+), 100 deletions(-)
--
2.34.1
next reply other threads:[~2022-11-06 21:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-06 21:28 Richard Henderson [this message]
2022-11-06 21:28 ` [PATCH v2 1/6] disas/nanomips: Move setjmp into nanomips_dis Richard Henderson
2022-11-06 21:28 ` [PATCH v2 2/6] disas/nanomips: Merge insn{1,2,3} into words[3] Richard Henderson
2022-11-06 21:28 ` [PATCH v2 3/6] disas/nanomips: Split out read_u16 Richard Henderson
2022-11-06 21:28 ` [PATCH v2 4/6] disas/nanomips: Tidy read for 48-bit opcodes Richard Henderson
2022-11-06 21:28 ` [PATCH v2 5/6] tcg: Move TCG_TARGET_HAS_direct_jump init to tb_gen_code Richard Henderson
2022-11-06 21:28 ` [PATCH v2 6/6] accel/tcg: Split out setjmp_gen_code Richard Henderson
2022-11-07 10:30 ` [PATCH v2 0/6] Two -Wclobbered fixes, plus other cleanup Philippe Mathieu-Daudé
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=20221106212852.152384-1-richard.henderson@linaro.org \
--to=richard.henderson@linaro.org \
--cc=balaton@eik.bme.hu \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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 NNTP newsgroup(s).