From: Pedro Alves <palves@redhat.com>
To: Yao Qi <qiyaoltc@gmail.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 2/6] Add constructor and destructor to regcache
Date: Thu, 27 Apr 2017 17:34:00 -0000 [thread overview]
Message-ID: <24c71239-5b8f-5ca1-a140-146acef9c543@redhat.com> (raw)
In-Reply-To: <1493152106-3246-3-git-send-email-yao.qi@linaro.org>
A few minor nits below, but looks good to me otherwise.
On 04/25/2017 09:28 PM, Yao Qi wrote:
> diff --git a/gdb/regcache.c b/gdb/regcache.c
> index 966f0c7..e0554c7 100644
> --- a/gdb/regcache.c
> +++ b/gdb/regcache.c
> @@ -191,6 +191,17 @@ regcache_register_size (const struct regcache *regcache, int n)
>
> struct regcache
> {
> +public:
> + explicit regcache (struct gdbarch *gdbarch, struct address_space *aspace_)
> + : regcache (gdbarch, aspace_, true)
There's no real good reason to use "explicit" when you have more than
one parameter.
> + {}
> +
> + ~regcache ()
> + {
> + xfree (registers);
> + xfree (register_status);
> + }
> +
> struct regcache_descr *descr;
>
> /* The address space of this register cache (for registers where it
> @@ -213,6 +224,33 @@ struct regcache
> /* If this is a read-write cache, which thread's registers is
> it connected to? */
> ptid_t ptid;
> +
> +private:
> + explicit regcache (struct gdbarch *gdbarch, struct address_space *aspace_,
> + bool readonly_p_)
Ditto.
> + : aspace (aspace_), readonly_p (readonly_p_)
> + {
> + gdb_assert (gdbarch != NULL);
> + descr = regcache_descr (gdbarch);
> +
> + if (readonly_p)
> + {
> + registers = XCNEWVEC (gdb_byte, descr->sizeof_cooked_registers);
> + register_status = XCNEWVEC (signed char,
> + descr->sizeof_cooked_register_status);
> + }
> + else
> + {
> + registers = XCNEWVEC (gdb_byte, descr->sizeof_raw_registers);
> + register_status = XCNEWVEC (signed char,
> + descr->sizeof_raw_register_status);
> + }
> + ptid = minus_one_ptid;
> + }
> +
> + friend struct regcache *
> + get_thread_arch_aspace_regcache (ptid_t ptid, struct gdbarch *gdbarch,
> + struct address_space *aspace);
> };
(I'd drop the "struct" in the aspace parameters.)
Thanks,
Pedro Alves
next prev parent reply other threads:[~2017-04-27 17:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 20:28 [PATCH 0/6] Class-fy regcache in GDB Yao Qi
2017-04-25 20:28 ` [PATCH 2/6] Add constructor and destructor to regcache Yao Qi
2017-04-27 17:34 ` Pedro Alves [this message]
2017-04-28 13:42 ` Yao Qi
2017-04-25 20:28 ` [PATCH 4/6] Simplify regcache_dup Yao Qi
2017-04-25 20:28 ` [PATCH 1/6 OBV] Change readonly_p to bool Yao Qi
2017-04-25 20:28 ` [PATCH 6/6] Remove cleanup in get_return_value Yao Qi
2017-04-25 20:29 ` [PATCH 5/6] Use copy ctor in regcache_dup Yao Qi
2017-04-27 17:37 ` Pedro Alves
2017-04-28 9:11 ` Yao Qi
2017-04-28 9:51 ` Pedro Alves
2017-04-28 13:20 ` Yao Qi
2017-04-25 20:29 ` [PATCH 3/6] Class-fy regcache Yao Qi
2017-04-27 17:35 ` Pedro Alves
2017-04-28 14:26 ` [PATCH 0/4 v2] Class-fy regcache in GDB Yao Qi
2017-04-28 14:26 ` [PATCH 4/4] Remove cleanup in get_return_value Yao Qi
2017-04-28 15:05 ` Pedro Alves
2017-04-28 14:26 ` [PATCH 1/4] Class-fy regcache Yao Qi
2017-04-28 15:03 ` Pedro Alves
2017-04-28 21:44 ` Yao Qi
2017-04-28 14:26 ` [PATCH 3/4] Use tag dispatch regcache ctor in regcache_dup Yao Qi
2017-04-28 15:04 ` Pedro Alves
2017-04-28 14:26 ` [PATCH 2/4] Simplify regcache_dup Yao Qi
2017-04-28 15:03 ` Pedro Alves
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=24c71239-5b8f-5ca1-a140-146acef9c543@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.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