From: Andreas Arnez <arnez@linux.vnet.ibm.com>
To: gdb-patches@sourceware.org
Cc: Yao Qi <yao@codesourcery.com>
Subject: [PATCH 08/12] NIOS2 Linux: Fill 'collect_regset' in regset structure.
Date: Mon, 26 May 2014 16:37:00 -0000 [thread overview]
Message-ID: <1401122208-2481-9-git-send-email-arnez@linux.vnet.ibm.com> (raw)
In-Reply-To: <1401122208-2481-1-git-send-email-arnez@linux.vnet.ibm.com>
gdb/
* nios2-linux-tdep.c (NIOS2_GREGS_SIZE): New macro.
(nios2_collect_gregset): New function.
(nios2_core_regset): Add collect method.
---
gdb/nios2-linux-tdep.c | 23 ++++++++++++++++++++---
1 file changed, 20 insertions(+), 3 deletions(-)
diff --git a/gdb/nios2-linux-tdep.c b/gdb/nios2-linux-tdep.c
index 84ab576..f4cacf6 100644
--- a/gdb/nios2-linux-tdep.c
+++ b/gdb/nios2-linux-tdep.c
@@ -51,6 +51,8 @@ static const int reg_offsets[NIOS2_NUM_REGS] =
-1, -1, -1, -1, -1, -1, -1, -1
};
+#define NIOS2_GREGS_SIZE (4 * 31)
+
/* Implement the supply_regset hook for core files. */
static void
@@ -73,11 +75,26 @@ nios2_supply_gregset (const struct regset *regset,
}
}
+static void
+nios2_collect_gregset (const struct regset *regset,
+ const struct regcache *regcache,
+ int regnum, void *gregs_buf, size_t len)
+{
+ gdb_byte *gregs = gregs_buf;
+ int regno;
+
+ for (regno = NIOS2_Z_REGNUM; regno <= NIOS2_MPUACC_REGNUM; regno++)
+ if (regnum == -1 || regnum == regno)
+ {
+ if (reg_offsets[regno] != -1)
+ regcache_raw_collect (regcache, regno,
+ gregs + 4 * reg_offsets[regno]);
+ }
+}
+
static const struct regset nios2_core_regset =
{
- NULL,
- nios2_supply_gregset,
- NULL,
+ NULL, nios2_supply_gregset, nios2_collect_gregset
};
/* Implement the regset_from_core_section gdbarch method. */
--
1.8.4.2
next prev parent reply other threads:[~2014-05-26 16:37 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 12/12] IA64 Linux: Define regset structures Andreas Arnez
2014-05-26 16:37 ` [PATCH 04/12] ALPHA Linux: Fill 'collect_regset' in " Andreas Arnez
2014-05-26 16:37 ` [PATCH 02/12] S390: Migrate to regcache_supply/collect_regset 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
2014-05-26 16:37 ` [PATCH 10/12] TILEGX Linux: Fill 'collect_regset' in regset structure Andreas Arnez
2014-05-26 16:37 ` [PATCH 09/12] SCORE: " 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 03/12] AARCH64 " Andreas Arnez
2014-05-27 21:36 ` Yufeng Zhang
2014-05-26 16:37 ` [PATCH 07/12] M32R Linux: Fill 'collect_regset' in regset structure Andreas Arnez
2014-05-26 16:37 ` [PATCH 11/12] M68K Linux: Define regset structures 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 05/12] FRV Linux: Fill 'collect_regset' in " Andreas Arnez
2014-05-26 16:37 ` Andreas Arnez [this message]
2014-05-27 2:15 ` [PATCH 08/12] NIOS2 Linux: Fill 'collect_regset' in regset structure Yao Qi
2014-06-02 9:09 ` 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=1401122208-2481-9-git-send-email-arnez@linux.vnet.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