From: Aleksandar Markovic <aleksandar.m.mail@gmail.com>
To: Alex Richardson <Alexander.Richardson@cl.cam.ac.uk>
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
Aleksandar Markovic <aleksandar.qemu.devel@gmail.com>,
Aleksandar Rikalo <aleksandar.rikalo@syrmia.com>,
Aurelien Jarno <aurelien@aurel32.net>,
"open list:All patches CC here" <qemu-devel@nongnu.org>
Subject: Re: [PATCH] Fix MIPS add.s after 1ace099f2acb952eaaef0ba7725879949a7e4406
Date: Tue, 7 Jul 2020 18:26:12 +0200 [thread overview]
Message-ID: <CAL1e-=huJ8hLCb7gG=cZ6bXcqMOUSA17NHpnCEED18MR4mKXhw@mail.gmail.com> (raw)
In-Reply-To: <20200703161515.25966-1-Alexander.Richardson@cl.cam.ac.uk>
On Fri, Jul 3, 2020 at 6:33 PM Alex Richardson
<Alexander.Richardson@cl.cam.ac.uk> wrote:
>
> After merging latest QEMU upstream into our CHERI fork, I noticed that
> some of the FPU tests in our MIPS baremetal testsuite
> (https://github.com/CTSRD-CHERI/cheritest) started failing. It turns out
> this commit accidentally changed add.s into a subtract.
>
> Signed-off-by: Alex Richardson <Alexander.Richardson@cl.cam.ac.uk>
> ---
Applied to MIPS + TCG Continuous Benchmarking queue.
> target/mips/fpu_helper.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/target/mips/fpu_helper.c b/target/mips/fpu_helper.c
> index 7a3a61cab3..56beda49d8 100644
> --- a/target/mips/fpu_helper.c
> +++ b/target/mips/fpu_helper.c
> @@ -1221,7 +1221,7 @@ uint32_t helper_float_add_s(CPUMIPSState *env,
> {
> uint32_t wt2;
>
> - wt2 = float32_sub(fst0, fst1, &env->active_fpu.fp_status);
> + wt2 = float32_add(fst0, fst1, &env->active_fpu.fp_status);
> update_fcr31(env, GETPC());
> return wt2;
> }
> --
> 2.27.0
>
>
next prev parent reply other threads:[~2020-07-07 16:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 16:15 [PATCH] Fix MIPS add.s after 1ace099f2acb952eaaef0ba7725879949a7e4406 Alex Richardson
2020-07-03 16:33 ` Aleksandar Markovic
2020-07-03 18:40 ` Philippe Mathieu-Daudé
2020-07-06 10:22 ` Alexander Richardson
2020-07-07 16:26 ` Aleksandar Markovic [this message]
2020-07-09 13:38 ` 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='CAL1e-=huJ8hLCb7gG=cZ6bXcqMOUSA17NHpnCEED18MR4mKXhw@mail.gmail.com' \
--to=aleksandar.m.mail@gmail.com \
--cc=Alexander.Richardson@cl.cam.ac.uk \
--cc=aleksandar.qemu.devel@gmail.com \
--cc=aleksandar.rikalo@syrmia.com \
--cc=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).