Bug 458305 - vmovdqa64 instruction is not supported
Summary: vmovdqa64 instruction is not supported
Status: RESOLVED DUPLICATE of bug 383010
Alias: None
Product: valgrind
Classification: Developer tools
Component: vex (show other bugs)
Version: 3.18.1
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-08-25 16:16 UTC by Tibor
Modified: 2024-02-25 02:10 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Vg error from log (1.36 KB, text/plain)
2022-08-25 16:16 UTC, Tibor
Details
Disassembly of the function with the unhandled isn (9.67 KB, text/plain)
2022-08-25 16:17 UTC, Tibor
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tibor 2022-08-25 16:16:25 UTC
Created attachment 151582 [details]
Vg error from log

SUMMARY
Valgrind 3.18.1 from conda-forge dies due to an unsupported instruction (vmovdqa64) when trying to run on a debug build of Psi4. Please see attached log excerpt and disassembly.

STEPS TO REPRODUCE
Getting a debug build of Psi4 is quite involved at the moment. Let me know if you really need it.

OBSERVED RESULT
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x8 0x6F 0x2 0xC5 0xF8 0x11 0x1
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

EXPECTED RESULT
All isns are handled?

SOFTWARE/OS VERSIONS
Ubuntu 20.04 LTS+HWE
Valgrind 3.18.1 obtained from conda-forge

ADDITIONAL INFORMATION
Intel Skylake-X CPU (supports AVX-512)
Comment 1 Tibor 2022-08-25 16:17:06 UTC
Created attachment 151583 [details]
Disassembly of the function with the unhandled isn
Comment 2 Paul Floyd 2022-08-26 14:47:29 UTC
This looks like a duplicate of https://bugs.kde.org/show_bug.cgi?id=383010

Could you try the patches there to confirm?
Comment 3 Paul Floyd 2022-09-26 08:32:24 UTC
No answer so I'm assuming this is a duplicate.

*** This bug has been marked as a duplicate of bug 383010 ***