From: Markus Deuling <deuling@de.ibm.com>
To: GDB Patches <gdb-patches@sourceware.org>
Cc: Ulrich Weigand <uweigand@de.ibm.com>
Subject: [rfc] [4/5] Get rid of current_gdbarch in reggroups.c
Date: Mon, 22 Oct 2007 10:00:00 -0000 [thread overview]
Message-ID: <471C7455.6090504@de.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 271 bytes --]
Hi,
this patch gets rid of some of the current_gdbarch's in reggroups.c
Is this ok to commit?
ChangeLog:
* reggroups.c (default_register_reggroup_p): Replace current_gdbarch
by gdbarch.
--
Markus Deuling
GNU Toolchain for Linux on Cell BE
deuling@de.ibm.com
[-- Attachment #2: diff-reggroups --]
[-- Type: text/plain, Size: 1023 bytes --]
diff -urpN src/gdb/reggroups.c dev/gdb/reggroups.c
--- src/gdb/reggroups.c 2007-08-23 20:08:36.000000000 +0200
+++ dev/gdb/reggroups.c 2007-10-22 11:36:15.000000000 +0200
@@ -157,8 +157,8 @@ default_register_reggroup_p (struct gdba
int float_p;
int raw_p;
- if (gdbarch_register_name (current_gdbarch, regnum) == NULL
- || *gdbarch_register_name (current_gdbarch, regnum) == '\0')
+ if (gdbarch_register_name (gdbarch, regnum) == NULL
+ || *gdbarch_register_name (gdbarch, regnum) == '\0')
return 0;
if (group == all_reggroup)
return 1;
@@ -166,7 +166,7 @@ default_register_reggroup_p (struct gdba
float_p = TYPE_CODE (register_type (gdbarch, regnum)) == TYPE_CODE_FLT;
/* FIXME: cagney/2003-04-13: Can't yet use gdbarch_num_regs
(gdbarch), as not all architectures are multi-arch. */
- raw_p = regnum < gdbarch_num_regs (current_gdbarch);
+ raw_p = regnum < gdbarch_num_regs (gdbarch);
if (group == float_reggroup)
return float_p;
if (group == vector_reggroup)
next reply other threads:[~2007-10-22 10:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-22 10:00 Markus Deuling [this message]
2007-10-22 14:40 ` Ulrich Weigand
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=471C7455.6090504@de.ibm.com \
--to=deuling@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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