Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 09/10] Move register_dump to regcache-dump.c
Date: Sat, 17 Feb 2018 03:50:00 -0000	[thread overview]
Message-ID: <9c0e590fd8e1d5d54a426aefe7c78650@polymtl.ca> (raw)
In-Reply-To: <1517999572-14987-10-git-send-email-yao.qi@linaro.org>

Hi Yao,

I think it would make sense to move the remaining dump-related things 
(the register_dump class, the register_dump::dump implementation) to 
regcache-dump.c.

For all empty destructors, you can use "= default" instead of {}.

> diff --git a/gdb/regcache-dump.c b/gdb/regcache-dump.c
> new file mode 100644
> index 0000000..4780fc4
> --- /dev/null
> +++ b/gdb/regcache-dump.c
> @@ -0,0 +1,335 @@
> +/* Copyright (C) 1986-2017 Free Software Foundation, Inc.
> +
> +   This file is part of GDB.
> +
> +   This program is free software; you can redistribute it and/or 
> modify
> +   it under the terms of the GNU General Public License as published 
> by
> +   the Free Software Foundation; either version 3 of the License, or
> +   (at your option) any later version.
> +
> +   This program is distributed in the hope that it will be useful,
> +   but WITHOUT ANY WARRANTY; without even the implied warranty of
> +   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
> +   GNU General Public License for more details.
> +
> +   You should have received a copy of the GNU General Public License
> +   along with this program.  If not, see 
> <http://www.gnu.org/licenses/>.  */
> +
> +#include "defs.h"
> +#include "gdbcmd.h"
> +#include "regcache.h"
> +#include "common/def-vector.h"
> +#include "valprint.h"
> +#include "remote.h"
> +#include "reggroups.h"
> +#include "target.h"
> +
> +/* Dump registers from regcache, used for dump raw registers and
> +   cooked registers.  */

I just saw it now, but you could say either "used for dumping" or "used 
to dump", but "for dump" doesn't sound right.

Simon


  reply	other threads:[~2018-02-17  3:50 UTC|newest]

Thread overview: 19+ 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 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 01/10] Class reg_buffer Yao Qi
2018-02-07 10:33 ` [PATCH 04/10] Class readonly_detached_regcache Yao Qi
2018-02-07 10:33 ` [PATCH 08/10] Remove regcache::m_readonly_p 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 09/10] Move register_dump to regcache-dump.c Yao Qi
2018-02-17  3:50   ` Simon Marchi [this message]
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
2018-02-07 10:33 ` [PATCH 07/10] No longer create readonly 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-17  3:53 ` [PATCH 00/10 v2] Remove regcache::m_readonly_p 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=9c0e590fd8e1d5d54a426aefe7c78650@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