| commit | a2a2d19f434380cd00fe31c9ea1734939eb2dadd | |
| author | Cyrill Gorcunov <gorcunov@gmail.com> | |
| Wed, 4 Nov 2015 22:14:05 +0000 (5 01:14 +0300) | ||
| committer | Cyrill Gorcunov <gorcunov@gmail.com> | |
| Wed, 4 Nov 2015 22:14:45 +0000 (5 01:14 +0300) | ||
| tree | 7fc4dd0cadbce7cd69adc90da3c4ec99a7722f1a | treesnapshot (tar.gz zip) |
| parent | 8aa9c2eb91b700a9dfdd587457d651f29499e816 | commitdiff |
disasm: Fix disassembling of evex prefix
As been pointed by @hpa evex is pretty fine in ia-32.
Quoting Peter
| This is wrong, though; EVEX is permitted in 32-bit mode just as VEX is.
| The key thing is that bits [7:5] have to be 1 in 32-bit mode. It is
| unclear what happens if these bits are 110 as that depends on if it is
| decoded using the modr/m decoder or not. For VEX prefixes we accept
| them as VEX in that case, which may not match the CPU.
This is a fix for commit db6ecf9b76a2
Reported-by: "H. Peter Anvin" <hpa@zytor.com>
Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
As been pointed by @hpa evex is pretty fine in ia-32.
Quoting Peter
| This is wrong, though; EVEX is permitted in 32-bit mode just as VEX is.
| The key thing is that bits [7:5] have to be 1 in 32-bit mode. It is
| unclear what happens if these bits are 110 as that depends on if it is
| decoded using the modr/m decoder or not. For VEX prefixes we accept
| them as VEX in that case, which may not match the CPU.
This is a fix for commit db6ecf9b76a2
Reported-by: "H. Peter Anvin" <hpa@zytor.com>
Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
| disasm.c | diffblobblamehistory |