https://bugs.kde.org/show_bug.cgi?id=328357
Török Edwin <edwin+...@etorok.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |edwin+...@etorok.net
--- Comment #8 from Török Edwin <edwin+...@etorok.net> ---
FWIW objdump 2.25.1 can decode these instructions.
$ valgrind /bin/ls
==6429== Memcheck, a memory error detector
==6429== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==6429== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==6429== Command: /bin/ls
==6429==
vex amd64->IR: unhandled instruction bytes: 0x8F 0xEA 0xF8 0x10 0xC6 0x5 0x3
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
==6429== valgrind: Unrecognised instruction at address 0x40e62c.
==6429== at 0x40E62C: ??? (in /bin/ls)
$ objdump -d /bin/ls|grep 40e62c
40e62c: 8f ea f8 10 c6 05 03 bextr $0x305,%rsi,%rax
As a workaround I can compile my code with '-march=native -mno-tbm' instead of
just '-march=native', but it would be nice if valgrind supported this
instruction:
https://bugs.gentoo.org/show_bug.cgi?id=563796
--
You are receiving this mail because:
You are watching all bug changes.
