From: Richard Henderson <richard.henderson@linaro.org>
To: Bastian Koppelmann <kbastian@mail.uni-paderborn.de>,
mjc@sifive.com, sagark@eecs.berkeley.edu, palmer@sifive.com,
Alistair.Francis@wdc.com
Cc: qemu-riscv@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] target/riscv: Bugfixes found in decodetree conversion
Date: Thu, 8 Nov 2018 16:53:49 +0100 [thread overview]
Message-ID: <97b143d6-5503-21ee-a836-cfa2597a5856@linaro.org> (raw)
In-Reply-To: <20181108120628.29926-1-kbastian@mail.uni-paderborn.de>
On 11/8/18 1:06 PM, Bastian Koppelmann wrote:
> while going through the reviews of the riscv-decodetree patches, two bugs came
> up that I fix here. There is one more problem [1] mentioned by Richard but
> I don't have the time to investigate it further.
>
> [1] https://patchwork.kernel.org/patch/10650293/
That one's not a bug, but an optimization.
The other bug mentioned is shrw and shaw not sign-extending the result.
r~
next prev parent reply other threads:[~2018-11-08 15:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 12:06 [Qemu-devel] [PATCH 0/2] target/riscv: Bugfixes found in decodetree conversion Bastian Koppelmann
2018-11-08 12:06 ` [Qemu-devel] [PATCH 1/2] target/riscv: Fix FCLASS_D being treated as RV64 only Bastian Koppelmann
2018-11-08 15:47 ` Richard Henderson
2018-11-13 20:06 ` Alistair Francis
2018-11-08 12:06 ` [Qemu-devel] [PATCH 2/2] target/riscv: Fix sfence.vm/a both available in any priv version Bastian Koppelmann
2018-11-08 15:43 ` Richard Henderson
2018-11-13 20:07 ` Alistair Francis
2018-11-08 15:53 ` Richard Henderson [this message]
2018-11-08 17:29 ` [Qemu-devel] [PATCH 0/2] target/riscv: Bugfixes found in decodetree conversion Bastian Koppelmann
2018-11-08 19:12 ` Palmer Dabbelt
2018-11-09 6:14 ` 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=97b143d6-5503-21ee-a836-cfa2597a5856@linaro.org \
--to=richard.henderson@linaro.org \
--cc=Alistair.Francis@wdc.com \
--cc=kbastian@mail.uni-paderborn.de \
--cc=mjc@sifive.com \
--cc=palmer@sifive.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=sagark@eecs.berkeley.edu \
/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).