Created attachment 179901 [details] configure output. When i run valgrind with i this error: vex amd64->IR: unhandled instruction bytes: 0x62 0xF2 0xFD 0x48 0x59 0x44 0x24 0x1 0x49 0x89 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 ==26057== valgrind: Unrecognised instruction at address 0x42f977. the related code at 0x42f977 is: ... 42f972: 4c 01 f8 add %r15,%rax 42f975: ff d0 call *%rax 42f977: 62 f2 fd 48 59 44 24 vpbroadcastq 0x8(%rsp),%zmm0 42f97e: 01 42f97f: 49 89 44 24 38 mov %rax,0x38(%r12) ... it is avx related code probably 512.. the version i encountered is 3.24.0 however i also build from git with head 19b70d65 (3.25.git). problem still there. i attached my configure log of ./configure --enable-inner --disable-ubsan --enable-lto --enable-tls --prefix=/home/kazim/.local/valgrind
You almost certainly don’t want —enable inner. LTO will make debugging Valgrind itself more difficult. And as for avx512, it’s not supported.
(In reply to Paul Floyd from comment #1) > You almost certainly don’t want —enable inner. > > LTO will make debugging Valgrind itself more difficult. i tried several parameters if it works. until i noticed it is related avx. > > And as for avx512, it’s not supported. Is there any plan to support?
(In reply to kazim sarikaya from comment #2) > (In reply to Paul Floyd from comment #1) > > And as for avx512, it’s not supported. > Is there any plan to support? There is https://bugs.kde.org/show_bug.cgi?id=valgrind-avx512 But nobody currently working on it. *** This bug has been marked as a duplicate of bug 383010 ***