This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH V4 8/8] Add MPX feature description to GDB manual.


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]