Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andreas Arnez <arnez@linux.vnet.ibm.com>
To: Yao Qi <yao@codesourcery.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH 01/12] regcache: Add functions suitable for regset_supply/collect.
Date: Tue, 27 May 2014 14:21:00 -0000	[thread overview]
Message-ID: <8738fv7166.fsf@br87z6lw.de.ibm.com> (raw)
In-Reply-To: <538482FD.3030104@codesourcery.com> (Yao Qi's message of "Tue, 27	May 2014 20:20:13 +0800")

On Tue, May 27 2014, Yao Qi wrote:

> On 05/27/2014 07:53 PM, Andreas Arnez wrote:
>> Correct.  Maybe it's better to rephrase the whole comment like this:
>> 
>
> Yes, that is much better.

Good -- thanks for pointing this out.

>
>> /* Mapping between register numbers and offsets in a buffer, for use
>>    in the '*regset' functions below.  In an array of
>>    'regcache_map_entry' each element is interpreted like follows:
>> 
>>    - If 'regno' is a register number: Map register 'regno' to the
>>      current offset (starting with 0) and increase the current offset
>>      by the register's size.  Repeat this with consecutive register
>>      numbers up to 'regno+count-1'.
>> 
>>    - If 'regno' has the special value REGCACHE_MAP_SKIP_BYTES: Add
>>      'count' to the current offset.
>
> Nit: I'd say "If 'regno' is REGCACHE_MAP_SKIP_BYTES, 'count' is the
> increased offset".  This is just my suggestion, which may be worse
> than yours.

I agree with simplifying the phrase "has the special value" to "is".
For consistency I'd like to stick to the term "current offset" from the
previous bullet.  Also, I intentionally avoid saying "increase", because
the current implementation allows 'count' to be negative.  So I'll just
shorten to:

  If 'regno' is REGCACHE_MAP_SKIP_BYTES: Add 'count' to the current
  offset.

>
>> 
>>    - If count=0: End of the map.  */
>> 
>>> >
>>>> >> +/* Transfer a set of registers (as described by REGSET) between
>>>> >> +   REGCACHE and BUF.  If REGNUM == -1, transfer all registers
>>>> >> +   belonging to the regset, otherwise just the register numbered
>>>> >> +   REGNUM.  The REGSET's 'descr' field must point to an array of
>>>> >> +   'struct regcache_map_entry'.
>>> >
>>> > IWBN to update the comments to 'descr' field, and go a step further,
>>> > rename field 'descr'.
>> With the new name being something like 'map' or 'regmap', I guess?  If
>> that's what you mean, I tend to agree, and I could provide a separate
>> patch for that.
>> 
>
> 'regmap' sounds good to me.  I don't have other comments.

OK, I'll post a separate patch for that.


  reply	other threads:[~2014-05-27 14:21 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-26 16:37 [PATCH 00/12] Regset rework preparations part 2 Andreas Arnez
2014-05-26 16:37 ` [PATCH 07/12] M32R Linux: Fill 'collect_regset' in regset structure Andreas Arnez
2014-05-26 16:37 ` [PATCH 03/12] AARCH64 Linux: Fill 'collect_regset' in regset structures Andreas Arnez
2014-05-27 21:36   ` Yufeng Zhang
2014-05-26 16:37 ` [PATCH 08/12] NIOS2 Linux: Fill 'collect_regset' in regset structure Andreas Arnez
2014-05-27  2:15   ` Yao Qi
2014-06-02  9:09     ` Andreas Arnez
2014-05-26 16:37 ` [PATCH 05/12] FRV Linux: Fill 'collect_regset' in regset structures Andreas Arnez
2014-05-26 16:37 ` [PATCH 11/12] M68K Linux: Define " Andreas Arnez
2014-05-27  1:37   ` Yao Qi
2014-05-27  8:51     ` Andreas Arnez
2014-05-27 12:48       ` Yao Qi
2014-05-26 16:37 ` [PATCH 12/12] IA64 " Andreas Arnez
2014-05-26 16:37 ` [PATCH 04/12] ALPHA Linux: Fill 'collect_regset' in " Andreas Arnez
2014-05-26 16:37 ` [PATCH 10/12] TILEGX Linux: Fill 'collect_regset' in regset structure Andreas Arnez
2014-05-26 16:37 ` [PATCH 06/12] HPPA Linux: Fill 'collect_regset' in regset structures Andreas Arnez
2014-05-26 16:37 ` [PATCH 09/12] SCORE: Fill 'collect_regset' in regset structure Andreas Arnez
2014-05-26 16:37 ` [PATCH 01/12] regcache: Add functions suitable for regset_supply/collect Andreas Arnez
2014-05-27  2:49   ` Yao Qi
2014-05-27 11:54     ` Andreas Arnez
2014-05-27 12:22       ` Yao Qi
2014-05-27 14:21         ` Andreas Arnez [this message]
2014-05-26 16:37 ` [PATCH 02/12] S390: Migrate to regcache_supply/collect_regset Andreas Arnez
2014-05-27  2:56 ` [PATCH 00/12] Regset rework preparations part 2 Yao Qi
2014-05-28 17:36   ` Andreas Arnez

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=8738fv7166.fsf@br87z6lw.de.ibm.com \
    --to=arnez@linux.vnet.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=yao@codesourcery.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