https://bugs.kde.org/show_bug.cgi?id=398545
--- Comment #8 from Macro Hoober <hy110...@foxmail.com> --- (In reply to Reini Urban from comment #5) > > How to add vex support for it? Sounds trivial. > > binutils/objdump can do it for a long time. > > I started with that at https://github.com/rurban/valgrind > linux names it sha_ni, freebsd SHA1,SHA2, > on Windows it's Family 3, cpu Model >= 92 on Intel and cpu Model >= 23 on > amd. > > But for adding the necessary logic stubs my 30 min self-intro into the code > is certainly not enough. There shouldn't be much logic needed I think. > Similar to the aesdec and crc insn, which do exist already. > I haven't even found the location where hwcaps are set. Thanks for the great work! After tested the patch "amd64: WIP start implementing the amd64 SHA extensions" based on 3.16.1 and get the error as following comments, https://github.com/rurban/valgrind/commit/f0fc15e32bba3fdd9d84e1ea7fd44916c4ff3d54 -- You are receiving this mail because: You are watching all bug changes.
