From: David Gibson <david@gibson.dropbear.id.au>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: qemu-ppc@nongnu.org, "Paul A. Clarke" <pc@us.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] ppc: Add support for 'mffsce' instruction
Date: Mon, 16 Sep 2019 10:25:07 +1000 [thread overview]
Message-ID: <20190916002507.GC2104@umbus.fritz.box> (raw)
In-Reply-To: <c39334e3-46f9-1973-11d0-c862ce80cc8b@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 2417 bytes --]
On Sat, Sep 14, 2019 at 01:00:21PM -0400, Richard Henderson wrote:
> On 9/12/19 8:54 AM, Paul A. Clarke wrote:
> > From: "Paul A. Clarke" <pc@us.ibm.com>
> >
> > ISA 3.0B added a set of Floating-Point Status and Control Register (FPSCR)
> > instructions: mffsce, mffscdrn, mffscdrni, mffscrn, mffscrni, mffsl.
> > This patch adds support for 'mffsce' instruction.
> >
> > 'mffsce' is identical to 'mffs', except that it also clears the exception
> > enable bits in the FPSCR.
> >
> > On CPUs without support for 'mffsce' (below ISA 3.0), the
> > instruction will execute identically to 'mffs'.
> >
> > Signed-off-by: Paul A. Clarke <pc@us.ibm.com>
> > ---
> > target/ppc/translate/fp-impl.inc.c | 30 ++++++++++++++++++++++++++++++
> > target/ppc/translate/fp-ops.inc.c | 2 ++
> > 2 files changed, 32 insertions(+)
> >
> > diff --git a/target/ppc/translate/fp-impl.inc.c b/target/ppc/translate/fp-impl.inc.c
> > index 59a4faf..34edc45 100644
> > --- a/target/ppc/translate/fp-impl.inc.c
> > +++ b/target/ppc/translate/fp-impl.inc.c
> > @@ -639,6 +639,36 @@ static void gen_mffsl(DisasContext *ctx)
> > tcg_temp_free_i64(t0);
> > }
> >
> > +/* mffsce */
> > +static void gen_mffsce(DisasContext *ctx)
> > +{
> > + TCGv_i64 t0;
> > + TCGv_i32 mask;
> > +
> > + if (unlikely(!(ctx->insns_flags2 & PPC2_ISA300))) {
> > + return gen_mffs(ctx);
> > + }
> > +
> > + if (unlikely(!ctx->fpu_enabled)) {
> > + gen_exception(ctx, POWERPC_EXCP_FPU);
> > + return;
> > + }
> > +
> > + t0 = tcg_temp_new_i64();
> > +
> > + gen_reset_fpstatus();
>
> Note for future cleanup: we should not need to sprinkle these all over. This
> should be the steady-state condition after softfp exceptions have been
> processed into powerpc exceptions, after every single fp instruction.
>
> That said, you're mirroring gen_mffs here, and the cleanup should
> happen globally.
This doesn't apply, presuambly because it's on top of the other
patch. So I'll wait for the respin that includes the small update
that rtc requested on that one.
>
> Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
>
>
> r~
>
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-09-16 0:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 12:54 [Qemu-devel] [PATCH] ppc: Add support for 'mffsce' instruction Paul A. Clarke
2019-09-14 17:00 ` Richard Henderson
2019-09-16 0:25 ` David Gibson [this message]
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=20190916002507.GC2104@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=pc@us.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=richard.henderson@linaro.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).