https://bugs.kde.org/show_bug.cgi?id=456948
--- Comment #8 from Mark Wielaard <m...@klomp.org> --- (In reply to f.roe...@magmasoft.de from comment #6) > Is this also a forbidden instruction? > vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0x7C 0x48 0x10 0x2 > 0x49 0x81 0xC0 0x0 > vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0 > vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE > vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0 > ==1112423== valgrind: Unrecognised instruction at address 0x1e74d9c0. > ==1112423== at 0x1E74D9C0: I_MPI_memcpy_nontemporal_avx512 (in > /net/aws1de027/data/repo_cache/mature/intelmpi_rt/2021.6.0/LINUX64_217/lib/ > libmpi.so.12) That looks like a avx52 variant of the MOVUPS instruction. Valgrind doesn't support that instruction. Yet see https://bugs.kde.org/show_bug.cgi?id=383010 Your program should first check the CPU supports such instructions before use. > I took https://github.com/pmem/valgrind/tree/pmem-3.19 and it worked better > than original 3.19 but also fails on some runs : ( Have you contacted the pmem valgrind developers to see if they want to contribute their improvements upstream? -- You are receiving this mail because: You are watching all bug changes.
