[valgrind] [Bug 357932] vex amd64->IR: unhandled instruction bytes: 0xF2 0x49 0xF 0x5D and 0xF2 0x49 0xF 0x5F

2016-10-19 Thread Julian Seward via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357932 Julian Seward changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[valgrind] [Bug 357932] vex amd64->IR: unhandled instruction bytes: 0xF2 0x49 0xF 0x5D and 0xF2 0x49 0xF 0x5F

2016-10-08 Thread Axel Müller via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357932 --- Comment #6 from Axel Müller --- The assembler code is from the Intel Performance Primitives (IPP) library when using the ippsLn_32f_A11 function (calculates natural logarithm). -- You are receiving this mail because: You are watching all bug chang

[valgrind] [Bug 357932] vex amd64->IR: unhandled instruction bytes: 0xF2 0x49 0xF 0x5D and 0xF2 0x49 0xF 0x5F

2016-09-23 Thread Julian Seward via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357932 --- Comment #5 from Julian Seward --- Mark, I think the patch is OK. In these insns we have, redundantly: REX.W=1, which says that this insn is 64-bits wide w.r.t. how it interacts with the integer register set, which is irrelevant because it doesn't

[valgrind] [Bug 357932] vex amd64->IR: unhandled instruction bytes: 0xF2 0x49 0xF 0x5D and 0xF2 0x49 0xF 0x5F

2016-09-22 Thread Mark Wielaard via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357932 --- Comment #4 from Mark Wielaard --- Or maybe Julian means the "redundant" REXB is altering the e register field and so it needs further adjustment to get the correct register if REXB is set. Anyway, a testcase and how to (or what) generates it would

[valgrind] [Bug 357932] vex amd64->IR: unhandled instruction bytes: 0xF2 0x49 0xF 0x5D and 0xF2 0x49 0xF 0x5F

2016-09-22 Thread Mark Wielaard via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357932 Mark Wielaard changed: What|Removed |Added CC||m...@redhat.com --- Comment #3 from Mark Wielaa

[valgrind] [Bug 357932] vex amd64->IR: unhandled instruction bytes: 0xF2 0x49 0xF 0x5D and 0xF2 0x49 0xF 0x5F

2016-09-09 Thread Axel Müller via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357932 --- Comment #2 from Axel Müller --- (In reply to Julian Seward from comment #1) > f2 49 0f 5d 00rex.WB minsd (%r8),%xmm0 > f2 49 0f 5f 00rex.WB maxsd (%r8),%xmm0 > > I'm sure these insns are handled really. It's just the redundant rex.

[valgrind] [Bug 357932] vex amd64->IR: unhandled instruction bytes: 0xF2 0x49 0xF 0x5D and 0xF2 0x49 0xF 0x5F

2016-07-20 Thread Julian Seward via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357932 --- Comment #1 from Julian Seward --- f2 49 0f 5d 00 rex.WB minsd (%r8),%xmm0 f2 49 0f 5f 00 rex.WB maxsd (%r8),%xmm0 I'm sure these insns are handled really. It's just the redundant rex.WB prefix that is causing them not to get de