All of lore.kernel.org
 help / color / mirror / Atom feed
From: Howard Spoelstra <hsp.cat7@gmail.com>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
	"qemu-devel qemu-devel" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v3 00/22] re-factor softfloat and add fp16 functions
Date: Thu, 25 Jan 2018 01:15:25 +0100	[thread overview]
Message-ID: <CABLmASFhcDY3RnBoo0Z_m-2wJsdjNYZm1dxuqMuxtz2VyjUCsA@mail.gmail.com> (raw)
In-Reply-To: <9cc3c0d8-26f4-5626-e0f1-e449068eaac1@linaro.org>

On Thu, Jan 25, 2018 at 1:09 AM, Richard Henderson
<richard.henderson@linaro.org> wrote:
> On 01/24/2018 01:49 PM, Howard Spoelstra wrote:
>> Hi,
>>
>> I built qemu-system-ppc for OSX and Windows from
>> https://github.com/stsquad/qemu/tree/softfloat-refactor-and-fp16-v3
>> and noticed a considerable drop in floating point performance on both
>> hosts.
>> Running Mac OS 9.2 in OSX, using MacBench 3.0, the score for the
>> floating point performance dropped from ~60 to ~42.
>>
>> Recent tcg optimisations had improved processor and floating point
>> performance considerably, but that gain seems to be more than lost for
>> the floating point performance.
>>
>> Any idea what is causing this?
>
> Is this a 64-bit or a 32-bit build?
>
> We made a conscious choice to share code and use all 64-bit operations, under
> the assumption that x86_64 is the most common host.
>
> Otherwise we have not really done extensive benchmarking.
>
>
> r~

Hi,

Both OSX and Windows builds are 64-bit.

Best,
Howard

  reply	other threads:[~2018-01-25  0:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-24 21:49 [Qemu-devel] [PATCH v3 00/22] re-factor softfloat and add fp16 functions Howard Spoelstra
2018-01-25  0:09 ` Richard Henderson
2018-01-25  0:15   ` Howard Spoelstra [this message]
2018-01-25 12:59 ` Alex Bennée
2018-01-28 20:41   ` Emilio G. Cota
2018-01-29 19:14     ` Richard Henderson
  -- strict thread matches above, loose matches on Subject: below --
2018-01-24 13:12 Alex Bennée
2018-01-24 13:42 ` 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=CABLmASFhcDY3RnBoo0Z_m-2wJsdjNYZm1dxuqMuxtz2VyjUCsA@mail.gmail.com \
    --to=hsp.cat7@gmail.com \
    --cc=alex.bennee@linaro.org \
    --cc=qemu-devel@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 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.