Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: DJBARROW@de.ibm.com
Cc: gdb-patches@sourceware.cygnus.com, s390-patches@gnu.org,
	schwidefsky@de.ibm.com, ARENZ@de.ibm.com
Subject: Re: New gdb 31 & 64 bit patches for S/390
Date: Wed, 04 Jul 2001 21:02:00 -0000	[thread overview]
Message-ID: <3B43DB38.5040702@cygnus.com> (raw)
In-Reply-To: <C1256A00.006F3FCE.00@d12mta09.de.ibm.com>

Hello,

I'm trying to understand the code:

+void
+_initialize_s390_tdep ()
+{
+  const bfd_arch_info_type *s390_arch_ptr =
+    bfd_lookup_arch (bfd_arch_s390, 0);
+
+#if GDB_MULTI_ARCH
+  /* Hook us into the gdbarch mechanism.  */
+  register_gdbarch_init (bfd_arch_s390, s390_gdbarch_init);
+#endif
+  if (!tm_print_insn)          /* Someone may have already set it */
+    tm_print_insn = gdb_print_insn_s390;
+  if (s390_arch_ptr)
+    tm_print_insn_info.mach = s390_arch_ptr->mach;
+  else
+    internal_error (__FILE__, __LINE__,
+                   "_initialize_s390_tdep: bfd_lookup_arch failed for ....
+}

but don't understand the reason for the call to bfd_lookup_arch().

printcmd.c:print_insn() will set the ->mach to the target architectures 
machine regardless of the above.

	Andrew


  parent reply	other threads:[~2001-07-04 21:02 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-27 12:39 DJBARROW
2001-02-28 16:13 ` Nick Clifton
2001-06-15  8:15 ` s390 readline; Was: " Andrew Cagney
2001-06-15 10:27   ` Elena Zannoni
2001-06-15 16:26     ` Elena Zannoni
2001-06-15  9:53 ` Andrew Cagney
2001-06-15 11:46   ` Andreas Jaeger
2001-06-15 12:22     ` Andrew Cagney
2001-06-15 12:18 ` [patch] Add predicate for EXTRACT_STRUCT_VALUE_ADDRESS; Was: " Andrew Cagney
2001-06-15 23:56   ` Eli Zaretskii
2001-06-28 16:58     ` Andrew Cagney
2001-06-28 23:21       ` Eli Zaretskii
2001-06-15 15:09 ` [patch] multi-arch ADDR_BITS_REMOVE; " Andrew Cagney
2001-06-15 16:09 ` [patch] multi-arch INIT_FRAME_PC*; " Andrew Cagney
2001-06-15 16:46 ` [patch] multi-arch CANNOT_^&*^*&_REGISTER(); " Andrew Cagney
2001-07-04 11:25 ` Andrew Cagney
2001-07-04 21:02 ` Andrew Cagney
2001-07-04 21:02 ` Andrew Cagney [this message]
2001-07-04 21:02 ` Andrew Cagney
2001-03-01  2:50 DJBARROW
2001-03-01 10:37 ` Nick Clifton
     [not found] <C1256A02.00573066.00@d12mta09.de.ibm.com>
2001-03-01 10:39 ` Nick Clifton
2001-06-18  3:32 DJBARROW
2001-07-05  3:12 Denis Joseph Barrow
2001-07-05  3:57 Denis Joseph Barrow
2001-07-05 10:11 ` Andrew Cagney
2001-07-05 10:11 ` Andrew Cagney
2001-07-05  5:04 Denis Joseph Barrow
2001-07-05  9:15 Denis Joseph Barrow
2001-07-05  9:19 Denis Joseph Barrow
2001-07-05 12:36 ` Andrew Cagney
2001-07-05 10:24 Denis Joseph Barrow
2001-07-05 12:46 ` Andrew Cagney
2001-07-08  0:53   ` Eli Zaretskii
2001-07-08 19:23     ` Andrew Cagney
2001-07-06  2:31 Denis Joseph Barrow
2001-08-13  3:06 Denis Joseph Barrow
2001-08-13  9:31 ` Andrew Cagney
2001-08-13  9:47 Denis Joseph Barrow
2001-08-15  2:22 Denis Joseph Barrow
2001-08-15  9:03 ` Andrew Cagney
2001-08-15  9:54 ` Andrew Cagney
     [not found] <OFEFF0AD94.761C34C1-ONC1256AB6.005503EE@de.ibm.com>
2001-08-28 16:33 ` Daniel Jacobowitz
2001-09-05 21:45   ` Andrew Cagney

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=3B43DB38.5040702@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=ARENZ@de.ibm.com \
    --cc=DJBARROW@de.ibm.com \
    --cc=gdb-patches@sourceware.cygnus.com \
    --cc=s390-patches@gnu.org \
    --cc=schwidefsky@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