doc: Document DEFAULT BND/NOBND in changes, add use case
Add DEFAULT BND/NOBND to the change history, and explain the use case.
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
diff --git a/doc/changes.src b/doc/changes.src
index a366c3f..ba3e7d3 100644
--- a/doc/changes.src
+++ b/doc/changes.src
@@ -50,6 +50,11 @@
\b Support \c{BND} prefix for branch instructions (for MPX).
+\b The \c{DEFAULT} directive can now take \c{BND} and \c{NOBND}
+options to indicate whether all relevant branches should be getting
+\c{BND} prefixes. This is expected to be the normal for use in MPX
+code.
+
\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.