On Tue, Jan 15, 2019 at 16:01:32 +0000, Alex Bennée wrote:
> Ahh I should have mentioned we already have the technology for this ;-)
>
> If you build the fpu/next tree on a s390x you can then run:
>
> ./tests/fp/fp-bench f64_div
>
> with and without the CONFIG_128 path. To get an idea of the real world
> impact you can compile a foreign binary and run it on a s390x system
> with:
>
> $QEMU ./tests/fp/fp-bench f64_div -t host
>
> And that will give you the peak performance assuming your program is
> doing nothing but f64_div operations. If the two QEMU's are basically in
> the same ballpark then it doesn't make enough difference. That said:
I think you mean here `tests/fp/fp-bench -o div -p double', otherwise
you'll get the default op (-o add).
Thanks,
E.
