diff options
| author | H. Peter Anvin <hpa@zytor.com> | 2013-12-31 10:38:51 -0800 |
|---|---|---|
| committer | H. Peter Anvin <hpa@zytor.com> | 2013-12-31 10:38:51 -0800 |
| commit | b2fcac9a1d54cf133160539ea64cbb27542d3c3f (patch) | |
| tree | dc77e8cdf28843b950ccb3567f8d542de960311e | |
| parent | be1d052fffdca447fe7a5af7cb02b7245be680d3 (diff) | |
| download | nasm-b2fcac9a1d54cf133160539ea64cbb27542d3c3f.tar.gz nasm-b2fcac9a1d54cf133160539ea64cbb27542d3c3f.tar.bz2 nasm-b2fcac9a1d54cf133160539ea64cbb27542d3c3f.zip | |
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>
| -rw-r--r-- | doc/changes.src | 5 | ||||
| -rw-r--r-- | doc/nasmdoc.src | 3 |
2 files changed, 8 insertions, 0 deletions
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 @@ This is expected to be most useful for the MPX instructions. \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. diff --git a/doc/nasmdoc.src b/doc/nasmdoc.src index dbf8e70..55a6313 100644 --- a/doc/nasmdoc.src +++ b/doc/nasmdoc.src @@ -4471,6 +4471,9 @@ be used. \c{DEFAULT NOBND} can disable \c{DEFAULT BND} and then \c{BND} prefix will be added only when explicitly specified in code. +\c{DEFAULT BND} is expected to be the normal configuration for writing +MPX-enabled code. + \H{section} \i\c{SECTION} or \i\c{SEGMENT}: Changing and \i{Defining Sections} |