From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [PATCH] rs6000-tdep.c: Use set_gdbarch_print_insn()
Date: Mon, 08 Apr 2002 17:13:00 -0000 [thread overview]
Message-ID: <1020409001204.ZM22336@localhost.localdomain> (raw)
I've just committed the patch below...
From Jimi X <jimix@watson.ibm.com>:
* rs6000-tdep.c (rs6000_gdbarch_init): Use set_gdbarch_print_insn().
Index: rs6000-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/rs6000-tdep.c,v
retrieving revision 1.45
diff -u -p -r1.45 rs6000-tdep.c
--- rs6000-tdep.c 8 Apr 2002 22:56:46 -0000 1.45
+++ rs6000-tdep.c 8 Apr 2002 23:52:06 -0000
@@ -2536,11 +2536,6 @@ rs6000_gdbarch_init (struct gdbarch_info
gdbarch = gdbarch_alloc (&info, tdep);
power = arch == bfd_arch_rs6000;
- /* Select instruction printer. */
- tm_print_insn = arch == power ? print_insn_rs6000 :
- info.byte_order == BFD_ENDIAN_BIG ? print_insn_big_powerpc :
- print_insn_little_powerpc;
-
/* Choose variant. */
v = find_variant_by_arch (arch, mach);
if (!v)
@@ -2585,6 +2580,14 @@ rs6000_gdbarch_init (struct gdbarch_info
tdep->regoff[i] = off;
off += regsize (v->regs + i, wordsize);
}
+
+ /* Select instruction printer. Note: tm_print_insn is still used by
+ gdbtk (insight), so we set both tm_print_insn and the gdbarch
+ method. */
+ tm_print_insn = arch == power ? print_insn_rs6000 :
+ info.byte_order == BFD_ENDIAN_BIG ? print_insn_big_powerpc :
+ print_insn_little_powerpc;
+ set_gdbarch_print_insn (gdbarch, tm_print_insn);
set_gdbarch_read_pc (gdbarch, generic_target_read_pc);
set_gdbarch_write_pc (gdbarch, generic_target_write_pc);
next reply other threads:[~2002-04-09 0:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-08 17:13 Kevin Buettner [this message]
2002-04-08 18:19 ` Elena Zannoni
2002-04-08 18:45 ` Kevin Buettner
2002-04-08 19:17 ` Kevin Buettner
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=1020409001204.ZM22336@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=gdb-patches@sources.redhat.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