From: Eli Zaretskii <eliz@gnu.org>
To: Stafford Horne <shorne@gmail.com>
Cc: gdb-patches@sourceware.org, simon.marchi@polymtl.ca
Subject: Re: [PATCH v4 1/4] reggroups: Add test and docs for `info reg $reggroup` feature
Date: Tue, 26 Dec 2017 15:56:00 -0000 [thread overview]
Message-ID: <837et9iiuj.fsf@gnu.org> (raw)
In-Reply-To: <20171226134832.23497-2-shorne@gmail.com> (message from Stafford Horne on Tue, 26 Dec 2017 22:48:29 +0900)
> From: Stafford Horne <shorne@gmail.com>
> Cc: Simon Marchi <simon.marchi@polymtl.ca>,
> Eli Zaretskii <eliz@gnu.org>,
> Stafford Horne <shorne@gmail.com>
> Date: Tue, 26 Dec 2017 22:48:29 +0900
>
> Until now this feature has existed but was not documented. Adding docs
> and tests.
>
> gdb/ChangeLog:
>
> yyyy-mm-dd Stafford Horne <shorne@gmail.com>
>
> * infcmd.c (_initialize_infcmd): Add help for info reg $reggroup
> and info all-registers $reggroup feature.
>
> gdb/doc/ChangeLog:
>
> yyyy-mm-dd Stafford Horne <shorne@gmail.com>
>
> * gdb.texinfo (Registers): Document info reg $reggroup feature.
>
> gdb/testsuite/ChangeLog:
>
> yyyy-mm-dd Stafford Horne <shorne@gmail.com>
>
> * gdb.base/reggroups.c: New file.
> * gdb.base/reggroups.exp: New file.
OK for the documentation parts, thanks.
next prev parent reply other threads:[~2017-12-26 15:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-26 13:48 [PATCH v4 0/4] Support for arbitrary reggroups Stafford Horne
2017-12-26 13:48 ` [PATCH v4 1/4] reggroups: Add test and docs for `info reg $reggroup` feature Stafford Horne
2017-12-26 15:56 ` Eli Zaretskii [this message]
2017-12-27 0:20 ` Simon Marchi
2017-12-27 14:34 ` Stafford Horne
2017-12-26 13:48 ` [PATCH v4 3/4] reggroups: Add reggroup_gdbarch_new, reggroup_find for dynamic reggroups Stafford Horne
2017-12-27 0:28 ` Simon Marchi
2017-12-26 13:48 ` [PATCH v4 2/4] reggroups: Convert reggroups from post_init to pre_init Stafford Horne
2017-12-26 13:49 ` [PATCH v4 4/4] tdesc: handle arbitrary strings in tdesc_register_in_reggroup_p Stafford Horne
2017-12-26 15:57 ` Eli Zaretskii
2017-12-27 0:30 ` Simon Marchi
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=837et9iiuj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=shorne@gmail.com \
--cc=simon.marchi@polymtl.ca \
/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).