https://bugs.kde.org/show_bug.cgi?id=487439
Mark Wielaard <m...@klomp.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |m...@klomp.org
--- Comment #8 from Mark Wielaard <m...@klomp.org> ---
(In reply to Paul Floyd from comment #5)
> This looks like
> 66 48 0f 73 f1 0c rex.W psllq xmm1,0xc
>
> Some more from the log
>
> vex amd64->IR: unhandled instruction bytes: 0x66 0x48 0xF 0x73 0xF1 0xC 0x66
> 0xF 0x70 0xF5
> vex amd64->IR: REX=1 REX.W=1 REX.R=0 REX.X=0 REX.B=0
> vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=0F
> vex amd64->IR: PFX.66=1 PFX.F2=0 PFX.F3=0
>
> "psllq" should be handled, but it looks like it's the REX prefix that is
> causing the problem.
I think we can just ignore the REX prefix. The intel 64 and IA-32
Architectures Software Developer’s Manual section 10.2.1 "Intel SSE in 64-Bit
Mode and Compatibility Mode" says:
"In 64-bit mode, eight additional XMM registers are accessible. Registers
XMM8-XMM15 are accessed by using REX prefixes. Memory operands are specified
using the ModR/M, SIB encoding described in Section 3.7.5. Some Intel SSE
instructions may be used to operate on general-purpose registers. Use the REX.W
prefix to access 64-bit general-purpose registers. Note that if a REX prefix is
used when it has no meaning, the prefix is ignored."
--
You are receiving this mail because:
You are watching all bug changes.
