diff options
| author | H. Peter Anvin <hpa@zytor.com> | 2008-06-11 18:52:54 -0700 |
|---|---|---|
| committer | H. Peter Anvin <hpa@zytor.com> | 2008-06-11 18:52:54 -0700 |
| commit | 593b73ae6d96f0288c94323d15b99ef2a2d3ddb1 (patch) | |
| tree | f6191c7e841e72fb01f2a345d8d0ceb0696d039c /doc | |
| parent | 7baaf630a57b844f060f34867e991aef2b70f507 (diff) | |
| download | nasm-593b73ae6d96f0288c94323d15b99ef2a2d3ddb1.tar.gz nasm-593b73ae6d96f0288c94323d15b99ef2a2d3ddb1.tar.bz2 nasm-593b73ae6d96f0288c94323d15b99ef2a2d3ddb1.zip | |
doc: title capitalization
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/nasmdoc.src | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/nasmdoc.src b/doc/nasmdoc.src index f86d36c..540ab01 100644 --- a/doc/nasmdoc.src +++ b/doc/nasmdoc.src @@ -4656,7 +4656,7 @@ qualifiers are: Any other section name is treated by default like \c{.text}. -\S{win32safeseh} \c{win32}: safe structured exception handling +\S{win32safeseh} \c{win32}: Safe Structured Exception Handling Among other improvements in Windows XP SP2 and Windows Server 2003 Microsoft has introduced concept of "safe structured exception @@ -4755,7 +4755,7 @@ with the exception that it is meant to target 64-bit code and the x86-64 platform altogether. This object file is used exactly the same as the \c{win32} object format (\k{win32fmt}), in NASM, with regard to this exception. -\S{win64pic} \c{win64}: writing position-independent code +\S{win64pic} \c{win64}: Writing Position-Independent Code While \c{REL} takes good care of RIP-relative addressing, there is one aspect that is easy to overlook for a Win64 programmer: indirect @@ -4823,7 +4823,7 @@ operand only: \c mov eax,label wrt ..imagebase ; ok \c mov rax,label wrt ..imagebase ; bad -\S{win64seh} \c{win64}: structured exception handling +\S{win64seh} \c{win64}: Structured Exception Handling Structured exception handing in Win64 is completely different matter from Win32. Upon exception program counter value is noted, and |