From: "Alex Bennée" <alex.bennee@linaro.org>
To: Dino Papararo <skizzato73@msn.com>
Cc: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Programmingkid <programmingkidx@gmail.com>,
"luoyonggang@gmail.com" <luoyonggang@gmail.com>,
"qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
Howard Spoelstra <hsp.cat7@gmail.com>
Subject: Re: R: R: About hardfloat in ppc
Date: Wed, 29 Apr 2020 19:25:30 +0100 [thread overview]
Message-ID: <87sggmjgit.fsf@linaro.org> (raw)
In-Reply-To: <AM4PR07MB350673696C7DE2CA16C9C685CAAD0@AM4PR07MB3506.eurprd07.prod.outlook.com>
Dino Papararo <skizzato73@msn.com> writes:
> Hi Alex,
<snip>
>
> I leave to you TCG's experts how it works and how to implement it, I'm
> only tryng to explain a possible fast way to go (if ever possible) 😊
This is all a theoretical discussion unless someone cares enough to
improve the situation. While I have an interest in improving TCG
performance I'm afraid there are many more easier wins before tackling a
target specific hack for which I'm not familiar. No doubt this thread
will be referred to next time someone wants something done about it.
> ..Large majority of software don't check for exceptions at all and if
> I really want to pursue max precision I'll go for a software
> multiprecision library like GMP or MPFR Libraries.
However for QEMU we regard failure to correctly emulate the architecture
as a bug - we don't code to common software patterns because there is
plenty of software out there that doesn't follow it.
> So the hardfloats 'should' be set as first choice and only if
> instruction requires precision/error check process it in softfloats.
Sure but someone will have to do the work to support that.
--
Alex Bennée
next prev parent reply other threads:[~2020-04-29 18:26 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
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 ` Alex Bennée [this message]
2020-04-30 0:20 ` R: " 罗勇刚(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=87sggmjgit.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=hsp.cat7@gmail.com \
--cc=luoyonggang@gmail.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=programmingkidx@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=skizzato73@msn.com \
/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).