OpenE2K
/
binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Fix the manual more thoroughly.

This commit is contained in:
Eli Zaretskii 2013-12-04 19:44:30 +02:00
parent 3ea8680f84
commit 22f25c9dd6
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
gdb/doc/gdb.texinfo
View File

@ -21393,10 +21393,9 @@ Show the current setting of the convention to return @code{struct}s
from functions.
@end table
@cindex Intel(R) Memory Protection Extensions (MPX).
@subsubsection Intel(R) @dfn{Memory Protection Extensions} (MPX).
@cindex Intel(R) Memory Protection Extensions (MPX).
@item bnd0raw..bnd3raw and bnd0@dots{}bnd3 registers display.
Memory Protection Extension (MPX) adds the bound registers @samp{BND0}
@footnote{The register named with capital letters represent the architecture
registers.} through @samp{BND3}. Bound registers store a pair of 64-bit values
@ -21421,10 +21420,11 @@ bnd0raw and bnd registers are presented as follows:
bnd0 = @{lbound = 0x32, ubound = 0x71@} : size 64
@end smallexample
This way the raw value can be accessed via bnd0raw@dots{}bnd3raw. Any change
on bnd0@dots{}bnd3 or bnd0raw@dots{}bnd3raw is reflect on its counterpart. When the
bnd0@dots{}bnd3 registers are displayed via Python, the display includes the memory size,
in bits, accessible to the pointer.
This way the raw value can be accessed via bnd0raw@dots{}bnd3raw. Any
change on bnd0@dots{}bnd3 or bnd0raw@dots{}bnd3raw is reflect on its
counterpart. When the bnd0@dots{}bnd3 registers are displayed via
Python, the display includes the memory size, in bits, accessible to
the pointer.
@node Alpha
@subsection Alpha