From: Richard Henderson <rth@twiddle.net>
To: qemu-devel@nongnu.org
Cc: alex.bennee@linaro.org, peter.maydell@linaro.org
Subject: [Qemu-devel] [PATCH 0/2] tcg/aarch64 fixes
Date: Wed, 7 Dec 2016 10:07:25 -0800 [thread overview]
Message-ID: <20161207180727.6286-1-rth@twiddle.net> (raw)
Both of these were identified by Alex and his risu testsuite, and diagnosed
by Peter. I believe that both bugs are my fault, originally.
The risu testsuite, as posted, now passes with an aarch64 host.
r~
Richard Henderson (2):
tcg/aarch64: Fix addsub2 for 0+C
tcg/aarch64: Fix tcg_out_movi
tcg/aarch64/tcg-target.inc.c | 66 ++++++++++++++++++++++----------------------
1 file changed, 33 insertions(+), 33 deletions(-)
--
2.9.3
next reply other threads:[~2016-12-07 18:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 18:07 Richard Henderson [this message]
2016-12-07 18:07 ` [Qemu-devel] [PATCH 1/2] tcg/aarch64: Fix addsub2 for 0+C Richard Henderson
2016-12-07 18:10 ` Peter Maydell
2016-12-07 18:15 ` Richard Henderson
2016-12-07 18:07 ` [Qemu-devel] [PATCH 2/2] tcg/aarch64: Fix tcg_out_movi Richard Henderson
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=20161207180727.6286-1-rth@twiddle.net \
--to=rth@twiddle.net \
--cc=alex.bennee@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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).