| commit | 6be432416fe5ebfbb31abfcbde1d2dc58185bd2d | [log] [tgz] |
|---|---|---|
| author | sewardj <sewardj@8f6e269a-dfd6-0310-a8e1-e2731360e62c> | Tue May 22 23:12:13 2012 +0000 |
| committer | sewardj <sewardj@8f6e269a-dfd6-0310-a8e1-e2731360e62c> | Tue May 22 23:12:13 2012 +0000 |
| tree | 17e50641aeaa61f74528424d60ea05653235dc07 | |
| parent | 80804d1d97fb9547a004b5246d5a1502650d643f [diff] |
Implement VMOVQ xmm1, r64 = VEX.128.66.0F.W1 7E /r (reg case only) If this is documented in the Intel manuals, I can't find it. GNU binutils and GDB seem to have heard of it, though. git-svn-id: svn://svn.valgrind.org/vex/trunk@2339 8f6e269a-dfd6-0310-a8e1-e2731360e62c