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

doc: title capitalization

Browse source
This commit is contained in:
H. Peter Anvin 2008-06-11 18:52:54 -07:00
parent f83781db62
commit 1b18ece43c
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
doc/nasmdoc.src
View file

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