From: Simon Marchi <simon.marchi@polymtl.ca>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 09/10] Move register_dump to regcache-dump.c
Date: Wed, 21 Feb 2018 14:49:00 -0000 [thread overview]
Message-ID: <f45a9a1bec95b38b2bc745f003e94330@polymtl.ca> (raw)
In-Reply-To: <CAH=s-PNfFBUypzyaOLspAi=F4HK9ZX_6-Ednh3dbEexUM71VWw@mail.gmail.com>
On 2018-02-21 08:58, Yao Qi wrote:
> On Wed, Feb 21, 2018 at 12:57 PM, Simon Marchi
> <simon.marchi@polymtl.ca> wrote:
>>>
>>> register_dump::dump accesses 'struct regcache_desc', which is
>>> declared in
>>> regcache.c, so that register_dump::dump can't be moved to
>>> regcache-dump.c.
>>
>>
>> Is there any reason we can't move struct regcache_descr to regcache.h?
>
> The reason I didn't move is that I want to keep regcache_descr opaque.
> To be clear, I don't mind moving regcache_descr to regcache.h and move
> all regcache dump stuff into regcache-dump.{c,h}.
I think it would make a more logical split, but I'll let you decide :)
next prev parent reply other threads:[~2018-02-21 14:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 10:33 [PATCH 00/10 v2] Remove regcache::m_readonly_p Yao Qi
2018-02-07 10:33 ` [PATCH 01/10] Class reg_buffer Yao Qi
2018-02-07 10:33 ` [PATCH 07/10] No longer create readonly regcache Yao Qi
2018-02-07 10:33 ` [PATCH 10/10] Pass readable_regcache to gdbarch method read_pc Yao Qi
2018-02-07 10:33 ` [PATCH 03/10] Remove regcache_save and regcache_cpy Yao Qi
2018-02-17 2:07 ` Simon Marchi
2018-02-07 10:33 ` [PATCH 04/10] Class readonly_detached_regcache Yao Qi
2018-02-07 10:33 ` [PATCH 05/10] Class detached_regcache Yao Qi
2018-02-17 3:15 ` Simon Marchi
2018-02-07 10:33 ` [PATCH 09/10] Move register_dump to regcache-dump.c Yao Qi
2018-02-17 3:50 ` Simon Marchi
2018-02-21 8:27 ` Yao Qi
2018-02-21 12:57 ` Simon Marchi
2018-02-21 13:59 ` Yao Qi
2018-02-21 14:49 ` Simon Marchi [this message]
2018-02-07 10:33 ` [PATCH 06/10] Replace regcache::dump with class register_dump Yao Qi
2018-02-07 10:33 ` [PATCH 02/10] class readable_regcache and pass readable_regcache to gdbarch pseudo_register_read and pseudo_register_read_value Yao Qi
2018-02-07 10:33 ` [PATCH 08/10] Remove regcache::m_readonly_p Yao Qi
2018-02-17 3:53 ` [PATCH 00/10 v2] " Simon Marchi
2018-02-21 11:22 ` Yao Qi
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=f45a9a1bec95b38b2bc745f003e94330@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).