From: "Emilio G. Cota" <cota@braap.org>
To: qemu-devel@nongnu.org
Cc: Richard Henderson <rth@twiddle.net>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: [Qemu-devel] [PATCHv2 0/2] target/sh4: translator loop conversion
Date: Mon, 19 Feb 2018 21:26:54 -0500 [thread overview]
Message-ID: <1519093616-10563-1-git-send-email-cota@braap.org> (raw)
Changes since v1:
- Instead of passing max_insns to tb_start, merge max_insns into base,
as suggested by Richard.
Note that I'm using an int, which is what all the callers were using
and is what the "bound" variables use too.
- Added rth's R-b tag to patch 2
I left out the suggestion of handling the gusa sequence in
translate_insn; I'm not very familiar with this code and don't have
a superh user-mode workload to test on.
Thanks,
Emilio
next reply other threads:[~2018-02-20 2:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 2:26 Emilio G. Cota [this message]
2018-02-20 2:26 ` [Qemu-devel] [PATCHv2 1/2] translator: merge max_insns into DisasContextBase Emilio G. Cota
2018-02-21 18:19 ` Richard Henderson
2018-02-21 20:17 ` Emilio G. Cota
2018-02-21 20:23 ` Richard Henderson
2018-02-20 2:26 ` [Qemu-devel] [PATCHv2 2/2] target/sh4: convert to TranslatorOps Emilio G. Cota
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=1519093616-10563-1-git-send-email-cota@braap.org \
--to=cota@braap.org \
--cc=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).