From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: cota@braap.org, Aurelien Jarno <aurelien@aurel32.net>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH v1 3/6] softfloat: enforce softfloat if the host's FMA is broken
Date: Tue, 08 Jan 2019 17:23:10 +0000 [thread overview]
Message-ID: <87h8ejukqp.fsf@linaro.org> (raw)
In-Reply-To: <20190108162154.22259-4-alex.bennee@linaro.org>
Alex Bennée <alex.bennee@linaro.org> writes:
> From: "Emilio G. Cota" <cota@braap.org>
>
> The added branch to the FMA ops is marked as unlikely and therefore
> its impact on performance (measured with fp-bench) is within noise range
> when measured on an Intel(R) Xeon(R) Gold 6142 CPU @ 2.60GHz.
Ahh I missed v2:
Subject: [PATCH v2] softfloat: enforce softfloat if the host's FMA is broken
Date: Tue, 25 Dec 2018 02:03:05 -0500
Message-Id: <20181225070305.18221-1-cota@braap.org>
I'll roll that into the next iteration.
--
Alex Bennée
next prev parent reply other threads:[~2019-01-08 17:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 16:21 [Qemu-devel] [PATCH v1 0/6] current fpu/next queue Alex Bennée
2019-01-08 16:21 ` [Qemu-devel] [PATCH v1 1/6] fp-bench: fix update_random_ops Alex Bennée
2019-01-08 16:21 ` [Qemu-devel] [PATCH v1 2/6] fp-bench: remove wrong exponent raise in fill_random Alex Bennée
2019-01-08 16:21 ` [Qemu-devel] [PATCH v1 3/6] softfloat: enforce softfloat if the host's FMA is broken Alex Bennée
2019-01-08 17:23 ` Alex Bennée [this message]
2019-01-08 16:21 ` [Qemu-devel] [PATCH v1 4/6] tests/Makefile: add floating point tests Alex Bennée
2019-01-09 21:08 ` Richard Henderson
2019-01-08 16:21 ` [Qemu-devel] [PATCH v1 5/6] scripts/archive-source: include softfloat tests Alex Bennée
2019-01-09 21:09 ` Richard Henderson
2019-01-08 16:21 ` [Qemu-devel] [PATCH v1 6/6] tests/Makfile: add check-softfloat rule Alex Bennée
2019-01-08 20:35 ` [Qemu-devel] [PATCH v1 0/6] current fpu/next queue no-reply
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=87h8ejukqp.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=aurelien@aurel32.net \
--cc=cota@braap.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@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).