procyberian/nasm
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

doc: Document DEFAULT BND/NOBND in changes, add use case

Browse source 
Add DEFAULT BND/NOBND to the change history, and explain the use case.

Signed-off-by: H. Peter Anvin <hpa@zytor.com>
This commit is contained in:
H. Peter Anvin 2013-12-31 10:38:51 -08:00
parent be1d052fff
commit b2fcac9a1d
2 changed files with 8 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
doc/changes.src
View file

@ -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.

3
doc/nasmdoc.src
View file

@ -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}