0xd4d

I tested the 32-bit disassembler too, it has many other unique failures: 32-bit code: - The 16-bit far call (1st instruction) isn't shown with a segment selector like the 2nd...

For completeness, I tested the 16-bit disassembler too. 16-bit code (protected mode): - Wrong target address ```diff -0010:877c 66e812345aa5 CALL 0xa55abb94 -0010:8782 66e85678a55a CALL 0x5aa5ffde +0010:877c 66e812345aa5 CALL SUB_a56a_bb94 +0010:8782...

Could be that clrmd is unable to read anything from the process. Updating to latest 1.x or trying 2.x could possibly fix that https://www.nuget.org/packages/Microsoft.Diagnostics.Runtime/

@glenn-slayden I had no problem building it without updating any source code. You can try this command since it will also checkout the clrmd submodule: `git clone --recursive https://github.com/drewnoakes/string-theory.git`

This is one of a few instructions that I've wanted to test on real HW but I don't have a VIA CPU. It's not 100% clear if they actually treat...

All reg kinds have their own struct so all mnemonic methods are smaller and easier to generate. The compiler can also check at compile time if it's a valid operand.

> I believe the SDM may be wrong for the 5th issue (EVEX.V' appears to be guarded in 32b mode). That instruction pattern generates an illegal instruction fault on real...

The CPUID feature bit is XOP so they shouldn't be supported by current and future AMD CPUs.

If they're encrypted they can probably not be decrypted anyway after saving it. AFAIK, ConfuserEx hashes part of the file and uses that as a key.

Have you had time to verify it yet? Otherwise I suggest you decrypt the methods first. I don't want to spend time on a feature that perhaps won't work.