Add {vex3} and {vex2} prefixes by analogy with {evex}
Allow specifying {vex3} or {vex2} (the latter is currently always
redundant, unless we end up with instructions at some point can be
specified with legacy prefixes or VEX) to select a specific encoding
of VEX-encoded instructions.
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
diff --git a/doc/changes.src b/doc/changes.src
index 91e3078..fcf6f2a 100644
--- a/doc/changes.src
+++ b/doc/changes.src
@@ -29,8 +29,9 @@
\b Support \c{BND} prefix for branch instructions
-\b Add \c{{evex}} instruction prefix to have nasm encode the corresponding
-instruction line with EVEX
+\b Add \c{{evex}}, \c{{vex3}} and \c{{vex2}} instruction prefixes to
+have NASM encode the corresponding instruction, if possible, with an EVEX,
+3-byte VEX, or 2-byte VEX prefix, respectively.
\b Ndisasm supports AVX-512/MPX/SHA instructions