From: Eli Zaretskii <eliz@gnu.org>
To: Walfred Tedeschi <walfred.tedeschi@intel.com>
Cc: palves@redhat.com, brobecker@adacore.com,
gdb-patches@sourceware.org, walfred.tedeschi@intel.com
Subject: Re: [PATCH V4 2/2] Add mpx-bnd-init-on-return set/show command for inferior calls.
Date: Wed, 02 Mar 2016 16:35:00 -0000 [thread overview]
Message-ID: <83ziug6dnw.fsf@gnu.org> (raw)
In-Reply-To: <1456935689-1820-3-git-send-email-walfred.tedeschi@intel.com> (message from Walfred Tedeschi on Wed, 2 Mar 2016 17:21:29 +0100)
> From: Walfred Tedeschi <walfred.tedeschi@intel.com>
> Cc: gdb-patches@sourceware.org, Walfred Tedeschi <walfred.tedeschi@intel.com>
> Date: Wed, 2 Mar 2016 17:21:29 +0100
>
> +While the using the @command{return} bounds can propagate through
> +execution causing a boundary violation.
This sentence needs to be rephrased.
> +@kindex set mpx-bnd-init-on-return
> +When set to true bound registers will be set to the INIT state when
> +using the "return" command.
> +@kindex show mpx-bnd-init-on-return
> +Show the state of mpx-bnd-init-on-return.
This last sentence should explain what is shown; just referring to the
variable name doesn't do the job.
> + add_setshow_boolean_cmd ("mpx-bnd-init-on-return", no_class,
> + &mpx_bnd_init_on_return, _("\
> + Set the bnd registers to INIT state when returning from a call."), _("\
> + Show the state of the mpx-bnd-init-on-return."),
For the 'show" part, we usually use the following wording:
Show whether to set the bnd registers to INIT state when returning from a call.
Thanks.
next prev parent reply other threads:[~2016-03-02 16:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 16:21 [PATCH V4 0/2] BND register initialization Walfred Tedeschi
2016-03-02 16:21 ` [PATCH V4 1/2] Initialize bnd register before performing inferior calls Walfred Tedeschi
2016-03-16 14:57 ` Luis Machado
2016-03-02 16:21 ` [PATCH V4 2/2] Add mpx-bnd-init-on-return set/show command for " Walfred Tedeschi
2016-03-02 16:35 ` Eli Zaretskii [this message]
2016-03-03 11:04 ` Walfred Tedeschi
2016-03-03 20:34 ` 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=83ziug6dnw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).