https://bugs.kde.org/show_bug.cgi?id=489221
--- Comment #5 from Mark Wielaard <m...@klomp.org> ---
This was implemented in:
commit 472b067e39a11a47ae3fa7cd7d3142558f78969d
Author: Julian Seward <jsew...@acm.org>
Date: Sun Mar 17 21:41:42 2019 +0100
amd64: Implement RDRAND, VCVTPH2PS and VCVTPS2PH.
Bug 398870 - Please add support for instruction vcvtps2ph
Bug 353370 - RDRAND amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7
0xF0
This commit implements:
* amd64 RDRAND instruction, on hosts that have it.
* amd64 VCVTPH2PS and VCVTPS2PH, on hosts that have it.
The presence/absence of these on the host is now reflected in the CPUID
results returned to the guest. So code that tests for these features in
CPUID and acts accordingly should "just work".
* New test cases, none/tests/amd64/rdrand and none/tests/amd64/f16c. These
are built if the host's assembler can handle them, in the usual way.
And on my machine the reproducer works just fine under valgrind.
If it still doesn't for you with latest valgrind could you run with valgrind -v
and check the hwcaps detect f16c:
--411301-- Arch and hwcaps: AMD64, LittleEndian,
amd64-cx16-lzcnt-rdtscp-sse3-ssse3-avx-avx2-bmi-f16c-rdrand-rdseed-fma
(and check your machine does actually have f16c set in /proc/cpuinfo)
--
You are receiving this mail because:
You are watching all bug changes.
