https://bugs.kde.org/show_bug.cgi?id=391148
Bug ID: 391148
Summary: Unhandled AVX instruction vmovq %xmm9,%xmm1
Product: valgrind
Version: 3.13.0
Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: vex
Assignee: jsew...@acm.org
Reporter: taku...@schaft-inc.com
Target Milestone: ---
I ran valgrind 3.13.0 with my AVX program and it died with this message.
vex amd64->IR: unhandled instruction bytes: 0xC5 0x79 0xD6 0xC9 0xC4 0xE3 0x7D
0x18 0xC1 0x1
vex amd64->IR: REX=0 REX.W=0 REX.R=1 REX.X=0 REX.B=0
vex amd64->IR: VEX=1 VEX.L=0 VEX.nVVVV=0x0 ESC=0F
vex amd64->IR: PFX.66=1 PFX.F2=0 PFX.F3=0
==17131== valgrind: Unrecognised instruction at address 0xe888c95.
I found the instruction was vmovq between xmm.
=> 0x000000000e888c95 <+213>: vmovq %xmm9,%xmm1
I can reproduce this problem by this code:
int main() {
asm("vmovq %xmm9, %xmm1");
return 0;
}
And found that "%xmm8, %xmm0" and "%xmm15, %xmm7" killed valgrind with similar
message but "%xmm15, %xmm8" didn't.
I also tried "%xmm0, %xmm8" and "%xmm8, %xmm9" and valgrind worked with them.
It seems valgrind cannot handle vmovq from xmm8-15 to xmm0-7.
--
You are receiving this mail because:
You are watching all bug changes.
