From: Omair Javaid <omair.javaid@linaro.org>
To: Andreas Arnez <arnez@linux.vnet.ibm.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Yao Qi <yao@codesourcery.com>, Mark Kettenis <kettenis@gnu.org>
Subject: Re: [PATCH v2 02/13] regcache: Add functions suitable for regset_supply/collect.
Date: Mon, 07 Jul 2014 09:32:00 -0000 [thread overview]
Message-ID: <CANW4E-0cEaQ=DLN5SVjWtCiHCK5iDDqUFnEgKbACig+pe4pW_A@mail.gmail.com> (raw)
In-Reply-To: <1403714949-28133-3-git-send-email-arnez@linux.vnet.ibm.com>
On 25 June 2014 21:48, Andreas Arnez <arnez@linux.vnet.ibm.com> wrote:
> These functions are intended to suit all targets that don't require too
> special logic in their regset supply/collect methods. Having such
> generic functions helps reducing target-specific complexity.
>
> gdb/
> * regcache.c: Include "regset.h".
> (regcache_supply_regset, regcache_collect_regset): New functions.
> * regcache.h (struct regcache_map_entry): New structure.
> (REGCACHE_MAP_SKIP_BYTES): New enum value.
> (regcache_supply_regset, regcache_collect_regset): New prototypes.
> ---
> gdb/regcache.c | 66 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> gdb/regcache.h | 44 +++++++++++++++++++++++++++++++++++++++
> 2 files changed, 110 insertions(+)
>
> diff --git a/gdb/regcache.c b/gdb/regcache.c
> index 5ee90b0..78fd962 100644
> --- a/gdb/regcache.c
> +++ b/gdb/regcache.c
> @@ -30,6 +30,7 @@
> #include "exceptions.h"
> #include "remote.h"
> #include "valprint.h"
> +#include "regset.h"
>
> /*
> * DATA STRUCTURE
> @@ -1068,6 +1069,71 @@ regcache_raw_collect (const struct regcache *regcache, int regnum, void *buf)
> memcpy (buf, regbuf, size);
> }
>
> +/* Supply register REGNUM from BUF to REGCACHE, using the register map
> + in REGSET. If REGNUM is -1, do this for all registers in
> + REGSET. */
> +
> +void
> +regcache_supply_regset (const struct regset *regset,
> + struct regcache *regcache,
> + int regnum, const void *buf, size_t size)
> +{
> + const struct regcache_map_entry *map = regset->regmap;
> + int offs = 0;
> + int i, count;
> +
> + for (i = 0; (count = map[i].count) != 0; i++)
> + {
> + int regno = map[i].regno;
> +
> + if (regno == REGCACHE_MAP_SKIP_BYTES)
> + offs += count;
> + else
> + for (; count--; regno++)
> + {
> + int new_offs = offs + regcache->descr->sizeof_register[regno];
> +
> + if (new_offs <= size && (regnum == -1 || regnum == regno))
> + regcache_raw_supply (regcache, regno,
> + buf ? (const gdb_byte *) buf + offs
> + : NULL);
> + offs = new_offs;
> + }
> + }
> +}
> +
> +/* Collect register REGNUM from REGCACHE to BUF, using the register
> + map in REGSET. If REGNUM is -1, do this for all registers in
> + REGSET. */
> +
> +void
> +regcache_collect_regset (const struct regset *regset,
> + const struct regcache *regcache,
> + int regnum, void *buf, size_t size)
> +{
> + const struct regcache_map_entry *map = regset->regmap;
> + int offs = 0;
> + int i, count;
> +
> + for (i = 0; (count = map[i].count) != 0; i++)
> + {
> + int regno = map[i].regno;
> +
> + if (regno == REGCACHE_MAP_SKIP_BYTES)
> + offs += count;
> + else
> + for (; count--; regno++)
> + {
> + int new_offs = offs + regcache->descr->sizeof_register[regno];
> +
> + if (new_offs <= size && (regnum == -1 || regnum == regno))
> + regcache_raw_collect (regcache, regno,
> + (gdb_byte *) buf + offs);
> + offs = new_offs;
> + }
> + }
> +}
> +
>
> /* Special handling for register PC. */
>
> diff --git a/gdb/regcache.h b/gdb/regcache.h
> index 8423f57..73ee043 100644
> --- a/gdb/regcache.h
> +++ b/gdb/regcache.h
> @@ -147,6 +147,50 @@ extern void regcache_raw_supply (struct regcache *regcache,
> extern void regcache_raw_collect (const struct regcache *regcache,
> int regnum, void *buf);
>
> +/* 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' is REGCACHE_MAP_SKIP_BYTES: Add 'count' to the current
> + offset.
> +
> + - If count=0: End of the map. */
> +
> +struct regcache_map_entry
> +{
> + int count;
> + int regno;
> +};
> +
> +/* Special value for the 'regno' field in the struct above. */
> +
> +enum
> + {
> + REGCACHE_MAP_SKIP_BYTES = -1,
> + };
> +
> +/* 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 'regmap' field must point to an array of
> + 'struct regcache_map_entry'.
> +
> + These functions are suitable for the 'regset_supply' and
> + 'regset_collect' fields in a regset structure. */
> +
> +extern void regcache_supply_regset (const struct regset *regset,
> + struct regcache *regcache,
> + int regnum, const void *buf,
> + size_t size);
> +extern void regcache_collect_regset (const struct regset *regset,
> + const struct regcache *regcache,
> + int regnum, void *buf, size_t size);
> +
>
> /* The type of a register. This function is slightly more efficient
> then its gdbarch vector counterpart since it returns a precomputed
> --
> 1.8.4.2
>
Is there a way around avoiding the loop in supply/collect where regnum
!= -1? It should be more efficient in cases where we are looking for a
register with regnum > 0.
next prev parent reply other threads:[~2014-07-07 9:32 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 16:49 [PATCH v2 00/13] Regset rework preparations part 2 Andreas Arnez
2014-06-25 16:49 ` [PATCH v2 08/13] M32R Linux: Fill 'collect_regset' in regset structure Andreas Arnez
2014-06-25 16:49 ` [PATCH v2 13/13] IA64 Linux: Define regset structures Andreas Arnez
2014-07-15 13:01 ` Ulrich Weigand
2014-07-18 9:06 ` Andreas Arnez
2014-06-25 16:49 ` [PATCH v2 10/13] SCORE: Fill 'collect_regset' in regset structure Andreas Arnez
2014-07-15 10:01 ` Ulrich Weigand
2014-07-15 12:25 ` Andreas Arnez
2014-06-25 16:49 ` [PATCH v2 09/13] NIOS2 Linux: " Andreas Arnez
2014-06-25 16:49 ` [PATCH v2 06/13] FRV Linux: Fill 'collect_regset' in regset structures Andreas Arnez
2014-06-25 16:49 ` [PATCH v2 03/13] S390: Migrate to regcache_supply/collect_regset Andreas Arnez
2014-07-15 9:27 ` Ulrich Weigand
2014-07-15 12:07 ` Andreas Arnez
2014-06-25 16:49 ` [PATCH v2 11/13] TILEGX Linux: Fill 'collect_regset' in regset structure Andreas Arnez
2014-07-15 10:12 ` Ulrich Weigand
2014-07-16 13:30 ` Andreas Arnez
2014-06-25 16:49 ` [PATCH v2 07/13] HPPA Linux: Fill 'collect_regset' in regset structures Andreas Arnez
2014-06-25 16:49 ` [PATCH v2 01/13] Rename 'descr' field in regset structure to 'regmap' Andreas Arnez
2014-06-25 16:49 ` [PATCH v2 12/13] M68K Linux: Define regset structures Andreas Arnez
2014-07-15 12:13 ` Ulrich Weigand
2014-07-16 18:01 ` Andreas Arnez
2014-06-25 16:49 ` [PATCH v2 02/13] regcache: Add functions suitable for regset_supply/collect Andreas Arnez
2014-07-07 9:32 ` Omair Javaid [this message]
2014-07-08 11:32 ` Andreas Arnez
2014-07-08 19:09 ` Omair Javaid
2014-07-10 7:54 ` Andreas Arnez
2014-07-19 13:10 ` Omair Javaid
2014-06-25 16:49 ` [PATCH v2 04/13] AARCH64 Linux: Fill 'collect_regset' in regset structures Andreas Arnez
2014-07-07 9:57 ` Omair Javaid
2014-06-25 16:49 ` [PATCH v2 05/13] ALPHA " Andreas Arnez
2014-07-01 8:00 ` [ping][PATCH v2 00/13] Regset rework preparations part 2 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='CANW4E-0cEaQ=DLN5SVjWtCiHCK5iDDqUFnEgKbACig+pe4pW_A@mail.gmail.com' \
--to=omair.javaid@linaro.org \
--cc=arnez@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=kettenis@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).