From: "Alex Bennée" <alex.bennee@linaro.org>
To: luoyonggang@gmail.com
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: About hardfloat in ppc
Date: Mon, 27 Apr 2020 10:42:41 +0100 [thread overview]
Message-ID: <87lfmhl0xa.fsf@linaro.org> (raw)
In-Reply-To: <CAE2XoE-ZSgtceSe5wYDm3cXf8+hTvJhD5PqZSrrFW5625LcSWg@mail.gmail.com>
罗勇刚(Yonggang Luo) <luoyonggang@gmail.com> writes:
> Because ppc fpu-helper are always clearing float_flag_inexact,
> So is that possible to optimize the performance when float_flag_inexact
> are cleared?
There was some discussion about this in the last thread about enabling
hardfloat for PPC. See the thread:
Subject: [RFC PATCH v2] target/ppc: Enable hardfloat for PPC
Date: Tue, 18 Feb 2020 18:10:16 +0100
Message-Id: <20200218171702.979F074637D@zero.eik.bme.hu>
However in short the problem is if the float_flag_inexact is clear you
must use softfloat so you can properly calculate the inexact status. We
can't take advantage of the inexact stickiness without loosing the
fidelity of the calculation.
--
Alex Bennée
next prev parent reply other threads:[~2020-04-27 9:43 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 6:39 About hardfloat in ppc 罗勇刚(Yonggang Luo)
2020-04-27 9:42 ` Alex Bennée [this message]
2020-04-27 10:34 ` BALATON Zoltan
2020-04-27 11:10 ` Alex Bennée
2020-04-27 21:18 ` 罗勇刚(Yonggang Luo)
2020-04-28 8:36 ` Alex Bennée
2020-04-28 14:29 ` 罗勇刚(Yonggang Luo)
2020-04-29 10:17 ` R: " Dino Papararo
2020-04-29 10:31 ` Dino Papararo
2020-04-29 11:57 ` Alex Bennée
2020-04-29 12:33 ` 罗勇刚(Yonggang Luo)
2020-04-29 13:38 ` Alex Bennée
2020-04-29 14:31 ` R: " Dino Papararo
2020-04-29 14:49 ` Peter Maydell
2020-04-29 18:25 ` R: " Alex Bennée
2020-04-30 0:20 ` 罗勇刚(Yonggang Luo)
2020-04-30 2:18 ` Richard Henderson
2020-04-30 7:26 ` 罗勇刚(Yonggang Luo)
2020-04-30 8:11 ` Alex Bennée
2020-04-30 8:13 ` 罗勇刚(Yonggang Luo)
2020-04-30 15:35 ` BALATON Zoltan
2020-04-30 16:34 ` R: " Dino Papararo
2020-05-01 1:59 ` Programmingkid
2020-05-01 2:21 ` 罗勇刚(Yonggang Luo)
2020-05-01 11:58 ` BALATON Zoltan
2020-05-01 12:04 ` 罗勇刚(Yonggang Luo)
2020-05-01 13:10 ` Alex Bennée
2020-05-01 13:39 ` BALATON Zoltan
2020-05-01 14:01 ` Alex Bennée
2020-05-01 14:18 ` Richard Henderson
2020-05-01 16:25 ` 罗勇刚(Yonggang Luo)
2020-05-01 19:33 ` Alex Bennée
2020-05-01 16:29 ` 罗勇刚(Yonggang Luo)
2020-05-01 16:51 ` Richard Henderson
2020-05-01 17:49 ` 罗勇刚(Yonggang Luo)
2020-05-01 20:35 ` Richard Henderson
2020-04-29 23:12 ` R: " 罗勇刚(Yonggang Luo)
2020-04-30 15:16 ` BALATON Zoltan
2020-04-30 18:59 ` Alex Bennée
2020-04-30 20:17 ` BALATON Zoltan
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=87lfmhl0xa.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=luoyonggang@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.