Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] rs6000-tdep.c: Use set_gdbarch_print_insn()
Date: Mon, 08 Apr 2002 19:17:00 -0000	[thread overview]
Message-ID: <1020409021634.ZM22922@localhost.localdomain> (raw)
In-Reply-To: Elena Zannoni <ezannoni@redhat.com> "Re: [PATCH] rs6000-tdep.c: Use set_gdbarch_print_insn()" (Apr  8,  9:18pm)

On Apr 8,  9:18pm, Elena Zannoni wrote:

> tm_print_insn shouldn't be used/needed anymore.  I have removed gdbtk's uses
> of tm_print_insn a while back.

I've just committed the following patch which takes care of this...

	* rs6000-tdep.c (rs6000_gdbarch_init): Don't set tm_print_insn;
	it's no longer required.

Index: rs6000-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/rs6000-tdep.c,v
retrieving revision 1.48
diff -u -p -r1.48 rs6000-tdep.c
--- rs6000-tdep.c	9 Apr 2002 01:41:46 -0000	1.48
+++ rs6000-tdep.c	9 Apr 2002 02:05:41 -0000
@@ -2458,6 +2458,7 @@ rs6000_gdbarch_init (struct gdbarch_info
   unsigned long mach;
   bfd abfd;
   int osabi, sysv_abi;
+  gdbarch_print_insn_ftype *print_insn;
 
   from_xcoff_exec = info.abfd && info.abfd->format == bfd_object &&
     bfd_get_flavour (info.abfd) == bfd_target_xcoff_flavour;
@@ -2574,13 +2575,14 @@ rs6000_gdbarch_init (struct gdbarch_info
       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);
+  /* Select instruction printer.  */
+  if (arch == power)
+    print_insn = print_insn_rs6000;
+  else if (info.byte_order == BFD_ENDIAN_BIG)
+    print_insn = print_insn_big_powerpc;
+  else
+    print_insn = print_insn_little_powerpc;
+  set_gdbarch_print_insn (gdbarch, print_insn);
 
   set_gdbarch_read_pc (gdbarch, generic_target_read_pc);
   set_gdbarch_write_pc (gdbarch, generic_target_write_pc);


      parent reply	other threads:[~2002-04-09  2:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-08 17:13 Kevin Buettner
2002-04-08 18:19 ` Elena Zannoni
2002-04-08 18:45   ` Kevin Buettner
2002-04-08 19:17   ` Kevin Buettner [this message]

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=1020409021634.ZM22922@localhost.localdomain \
    --to=kevinb@redhat.com \
    --cc=ezannoni@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