[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug binutils/16891] libopcodes decodes x86 26 9B as 'fwait' not 'es'
From: |
rsc at swtch dot com |
Subject: |
[Bug binutils/16891] libopcodes decodes x86 26 9B as 'fwait' not 'es' |
Date: |
Thu, 01 May 2014 05:22:17 +0000 |
https://sourceware.org/bugzilla/show_bug.cgi?id=16891
--- Comment #1 from Russ Cox <rsc at swtch dot com> ---
Here are some related cases. They may be caused by something slightly
different, since FWAIT is so special, but it didn't seem worth filing a new
bug.
The format is: <hex bytes>: <correct answer> vs <libopcodes output>. I am
claiming to know the <correct answer> because libopcodes is choosing to treat
the instruction as a single byte. If so, I believe that it should describe the
first input byte.
66 67 ad 66 77 88 00 00: data16 vs addr16
66 f0 5f 66 77 88 00 00: data16 vs lock
f2 66 67 f0 0f 11 22 00: repnz vs data16
f2 67 ad 66 77 88 00 00: repnz vs addr16
f2 f0 36 66 67 0f 11 22: repnz vs lock
f3 66 67 f0 0f 11 22 00: repz vs data16
f3 67 ad 66 77 88 00 00: repz vs addr16
f3 f0 5f 66 77 88 00 00: repz vs lock
f3 f2 5f 66 77 88 00 00: repz vs repnz
--
You are receiving this mail because:
You are on the CC list for the bug.
- [Bug binutils/16891] libopcodes decodes x86 26 9B as 'fwait' not 'es',
rsc at swtch dot com <=