diff options
| author | iximeow <me@iximeow.net> | 2019-12-16 01:02:56 -0800 |
|---|---|---|
| committer | iximeow <me@iximeow.net> | 2020-01-12 16:10:14 -0800 |
| commit | a245487fa29f7e132f6f2c42d84bdaf5fc099922 (patch) | |
| tree | d900102ad44671fddc0df8db1fb585ade4adc9b4 /src/vex.rs | |
| parent | f23d12996aeb4f6e1dbf65e4c8e39376303425c8 (diff) | |
support aesni
this includes respecting ModRM_XXXX-style operand codes from alternate
0f opcode maps. this MAY introduce bugs where an opcode 0fXX is valid
by the 0f map, invalid by the 660f map, and we see a sequence like
660fXXYY. if YY results in 0fXX being invalid by 660f, we may have to
fall back to reading opcode XX as an 0f opcode, where YY needs to be
re-read with the correct operand code.
hopefully this doesn't actually happen...
Diffstat (limited to 'src/vex.rs')
0 files changed, 0 insertions, 0 deletions