[valgrind] [Bug 212352] vex amd64 unhandled opc_aux = 0x 2, first_opcode == 0xDC (FCOM)

[Tom Hughes via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=212352

Tom Hughes  changed:

   What|Removed |Added

 CC||t...@compton.nu

--- Comment #2 from Tom Hughes  ---
Committed as VEX r3207 with tests in valgrind r15779.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 212352] vex amd64 unhandled opc_aux = 0x 2, first_opcode == 0xDC (FCOM)

[Tom Hughes via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=212352

Tom Hughes  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 212352] vex amd64 unhandled opc_aux = 0x 2, first_opcode == 0xDC (FCOM)

[Mark Harris via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=212352

--- Comment #1 from Mark Harris  ---
Would it be possible to merge this patch implementing the unhandled FCOM
instruction?  It's the exact code used for FCOMP except with no fp_pop().

As for the comment which is part of the existing FCOMP code about C1 being set
to 0, both the Intel and AMD docs show that FCOM and FCOMP are supposed to set
C1 to 0, so if there is a concern there it is not clear what it is.

-- 
You are receiving this mail because:
You are watching all bug changes.