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-15 21:20:59 -0700 |
| commit | 1b18ece43c7b367121b9b7889afe256214e9a2d2 (patch) | |
| tree | cd14ef86803964effa19c1ab62be688fb2bca3e3 | |
| parent | f83781db62f2b7b32d111c456b76fca09bfd6854 (diff) | |
| download | nasm-1b18ece43c7b367121b9b7889afe256214e9a2d2.tar.gz | |
doc: title capitalization
| -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 4601e56c..07aa0747 100644 --- a/doc/nasmdoc.src +++ b/doc/nasmdoc.src @@ -4645,7 +4645,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 @@ -4744,7 +4744,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 @@ -4812,7 +4812,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 |