Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Walfred Tedeschi <walfred.tedeschi@intel.com>
To: eliz@gnu.org
Cc: gdb-patches@sourceware.org,
	Walfred Tedeschi <walfred.tedeschi@intel.com>
Subject: [OBV PATCH] MPX documentation
Date: Thu, 17 Dec 2015 13:24:00 -0000	[thread overview]
Message-ID: <1450358668-11765-1-git-send-email-walfred.tedeschi@intel.com> (raw)

Fix some trademarks on MPX section.

2015-12-15  Walfred Tedeschi  <walfred.tedeschi@intel.com>

doc:
   	gdb.texinfo: (Intel(R) Memory Protection Extensions): Fix
	trademarks.

---
 gdb/doc/gdb.texinfo | 19 ++++++++++---------
 1 file changed, 10 insertions(+), 9 deletions(-)

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index fd7fc24..43e13bf 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -22013,15 +22013,16 @@ from functions.
 
 
 @subsubsection Intel(R) @dfn{Memory Protection Extensions} (MPX).
-@cindex Intel(R) Memory Protection Extensions (MPX).
-
-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
-which are the lower bound and upper bound.  Bounds are effective addresses or
-memory locations.  The upper bounds are architecturally represented in 1's
-complement form.  A bound having lower bound = 0, and upper bound = 0
-(1's complement of all bits set) will allow access to the entire address space.
+@cindex Intel(R) Memory Protection Extensions (Intel(R) MPX).
+
+Intel(R) Memory Protection Extension (Intel(R) 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 which are the lower bound
+and upper bound.  Bounds are effective addresses or memory locations.
+The upper bounds are architecturally represented in 1's complement form.
+A bound having lower bound = 0, and upper bound = 0 (1's complement of
+all bits set) will allow access to the entire address space.
 
 @samp{BND0} through @samp{BND3} are represented in @value{GDBN} as @samp{bnd0raw}
 through @samp{bnd3raw}.  Pseudo registers @samp{bnd0} through @samp{bnd3}
-- 
2.1.4


             reply	other threads:[~2015-12-17 13:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-17 13:24 Walfred Tedeschi [this message]
2015-12-17 16:19 ` Eli Zaretskii
2015-12-17 18:05   ` Joseph Myers
2015-12-18  7:48     ` Tedeschi, Walfred
2015-12-21 13:48       ` Pedro Alves
2015-12-21 15:39         ` Eli Zaretskii
2015-12-21 17:38           ` Pedro Alves
2016-01-11 11:42           ` Pedro Alves
2016-01-11 12:35             ` Tedeschi, Walfred
2016-01-11 14:07               ` Pedro Alves
2016-01-11 15:41             ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1450358668-11765-1-git-send-email-walfred.tedeschi@intel.com \
    --to=walfred.tedeschi@intel.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox