From: Eli Zaretskii <eliz@gnu.org>
To: Walfred Tedeschi <walfred.tedeschi@intel.com>
Cc: tromey@redhat.com, gdb-patches@sourceware.org,
mark.kettenis@xs4all.nl, walfred.tedeschi@intel.com
Subject: Re: [PATCH V4 8/8] Add MPX feature description to GDB manual.
Date: Thu, 05 Sep 2013 09:37:00 -0000 [thread overview]
Message-ID: <831u53d2ys.fsf@gnu.org> (raw)
In-Reply-To: <1378373188-31144-9-git-send-email-walfred.tedeschi@intel.com>
> From: Walfred Tedeschi <walfred.tedeschi@intel.com>
> Cc: Walfred Tedeschi <walfred.tedeschi@intel.com>
> Date: Thu, 5 Sep 2013 11:26:28 +0200
>
> diff --git a/gdb/NEWS b/gdb/NEWS
> index ca8baea..fc58cc4 100644
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -5464,3 +5464,5 @@ GDB now handles cross debugging. If you are remotely debugging between
> two different machines, type ``./configure host -target=targ''.
> Host is the machine where GDB will run; targ is the machine
> where the program that you are debugging will run.
> +
> + * GDB now supports access to Intel(R) MPX registers on GNU/Linux.
This part is OK.
> +@samp{bnd0raw} through @samp{bnd3raw} for i386, amd64 and x32. Hardware
> +representation of the bound registers effectively @samp{bnd0} through
What does "effectively" mean in this context?
> +@samp{bnd3}. The bounds are unsigned effective addresses, and are
And what does "effective" mean here?
> +inclusive. The upper bounds are architecturally represented in 1's
^^
Two spaces are needed here.
> +User representation of the bound registers. Upper bound value stores
> +the effective address of the bound, i.e. the one's complement of the
Same question about "effective". Also, please insert either a comma
',' or @: after "i.e.", to make sure the second period is not rendered
by TeX as an end of a sentence.
Thanks.
next prev parent reply other threads:[~2013-09-05 9:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 9:26 [PATCH V4 0/8] Intel(R) MPX register support Walfred Tedeschi
2013-09-05 9:26 ` [PATCH V4 4/8] MPX for amd64 Walfred Tedeschi
2013-09-10 12:48 ` Mark Kettenis
2013-09-10 14:56 ` Walfred Tedeschi
2013-09-12 8:53 ` Tedeschi, Walfred
2013-09-05 9:26 ` [PATCH V4 3/8] Add MPX support for i386 Walfred Tedeschi
2013-09-05 9:40 ` Eli Zaretskii
2013-09-06 7:36 ` Tedeschi, Walfred
2013-09-05 9:26 ` [PATCH V4 1/8] Fix conditions in creating a bitfield Walfred Tedeschi
2013-09-05 9:26 ` [PATCH V4 2/8] Add MPX registers XML files Walfred Tedeschi
2013-09-05 9:26 ` [PATCH V4 7/8] Add MPX registers tests Walfred Tedeschi
2013-09-05 9:26 ` [PATCH V4 8/8] Add MPX feature description to GDB manual Walfred Tedeschi
2013-09-05 9:37 ` Eli Zaretskii [this message]
2013-09-05 9:26 ` [PATCH V4 5/8] Add MPX support to gdbserver Walfred Tedeschi
2013-09-05 9:26 ` [PATCH V4 6/8] Add pretty-printer for MPX bnd registers Walfred Tedeschi
2013-09-05 9:41 ` [PATCH V4 0/8] Intel(R) MPX register support Eli Zaretskii
[not found] ` <AC542571535E904D8E8ADAE745D60B191B18DB69@IRSMSX104.ger.corp.intel.com>
2013-09-09 16:32 ` Eli Zaretskii
2013-09-25 11:51 ` Tedeschi, Walfred
2013-09-25 12:33 ` Eli Zaretskii
2013-09-25 12:41 ` Tedeschi, Walfred
2013-09-25 15:37 ` Eli Zaretskii
2013-09-25 12:47 ` Mark Kettenis
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=831u53d2ys.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=tromey@redhat.com \
--cc=walfred.tedeschi@intel.com \
/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