From: Michael Clark <mjc@sifive.com>
To: qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Cc: patches@groups.riscv.org, Michael Clark <mjc@sifive.com>
Subject: [Qemu-devel] [PULL 0/2] RISC-V: Important fixes for QEMU 2.12
Date: Wed, 28 Mar 2018 13:40:17 -0700 [thread overview]
Message-ID: <1522269619-48636-1-git-send-email-mjc@sifive.com> (raw)
The following changes since commit 043289bef4d9c0d277c45695c676a6cc9fca48a0:
Merge remote-tracking branch 'remotes/rth/tags/pull-tcg-20180328' into staging (2018-03-28 13:30:10 +0100)
are available in the git repository at:
https://github.com/riscv/riscv-qemu.git tags/riscv-qemu-2.12-important-fixes
for you to fetch changes up to 33b4f859f1e1ea6722d10c3e9c0e3d85afb44ff4:
RISC-V: Fix incorrect disassembly for addiw (2018-03-28 11:12:02 -0700)
----------------------------------------------------------------
RISC-V: Important fixes for QEMU 2.12
This series includes changes that are considered important.
i.e. correct user-visible bugs that are exercised by common
operations such as -cpu list (CPU model changes) or -d in_asm
(fix for disassembly of addiw)
----------------------------------------------------------------
Michael Clark (2):
RISC-V: Convert cpu definition to future model
RISC-V: Fix incorrect disassembly for addiw
disas/riscv.c | 2 +-
target/riscv/cpu.c | 123 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++---------------------------------------------------
2 files changed, 70 insertions(+), 55 deletions(-)
next reply other threads:[~2018-03-28 20:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 20:40 Michael Clark [this message]
2018-03-28 20:40 ` [Qemu-devel] [PULL 1/2] RISC-V: Convert cpu definition to future model Michael Clark
2018-03-28 20:40 ` [Qemu-devel] [PULL 2/2] RISC-V: Fix incorrect disassembly for addiw Michael Clark
2018-03-29 10:21 ` [Qemu-devel] [PULL 0/2] RISC-V: Important fixes for QEMU 2.12 Peter Maydell
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=1522269619-48636-1-git-send-email-mjc@sifive.com \
--to=mjc@sifive.com \
--cc=patches@groups.riscv.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).