From: Eli Zaretskii <eliz@gnu.org>
To: Walfred Tedeschi <walfred.tedeschi@intel.com>
Cc: palves@redhat.com, qiyaoltc@gmail.com, brobecker@adacore.com,
gdb-patches@sourceware.org
Subject: Re: [PATCH V8] amd64-mpx: initialize BND register before performing inferior calls.
Date: Tue, 21 Feb 2017 17:06:00 -0000 [thread overview]
Message-ID: <83lgszo4nd.fsf@gnu.org> (raw)
In-Reply-To: <1487695238-15286-1-git-send-email-walfred.tedeschi@intel.com> (message from Walfred Tedeschi on Tue, 21 Feb 2017 17:40:38 +0100)
> From: Walfred Tedeschi <walfred.tedeschi@intel.com>
> Cc: gdb-patches@sourceware.org, Walfred Tedeschi <walfred.tedeschi@intel.com>
> Date: Tue, 21 Feb 2017 17:40:38 +0100
>
> +On the other hand you can also examine the influence of the bound register in
> +the execution of the function, i.e. verify if modifying bounds would cause bound
^^^^
Either "i.e.,", with a comma, or "i.e.@:", so that TeX doesn't decide
this ends a sentence.
> +viaolations and how. You can achieve this by stoppying the execution of the
^^^^^^^^^^^ ^^^^^^^^^
Typos.
> +called function at its prologue and setting the bnd registers continuing then
^^^
Wrong letter-case? a typo?
> +the execution. See the example below:
^^
Two spaces here, please.
> +At this last step the value of bnd0 can be changed for investigation of bound
> +violations caused along the execution of the call. In order to know how to
> +set the bnd registers or bound table for the call consult the ABI.
^^^
"bound"?
Thanks.
next prev parent reply other threads:[~2017-02-21 17:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 16:41 Walfred Tedeschi
2017-02-21 17:03 ` Eli Zaretskii
2017-02-22 10:15 ` Tedeschi, Walfred
2017-02-21 17:06 ` Eli Zaretskii [this message]
2017-02-24 14:40 ` Pedro Alves
2017-02-24 15:03 ` Tedeschi, Walfred
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=83lgszo4nd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=qiyaoltc@gmail.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