Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Volkov <Andrew.Volkov@transas.com>
To: binutils@sources.redhat.com, gdb-patches@sources.redhat.com
Cc: Alan Modra <amodra@bigpond.net.au>, Andrew Cagney <ac131313@cygnus.com>
Subject: [patch/rfa] cpu-h8300.c move default target to begin of list
Date: Tue, 28 May 2002 08:50:00 -0000	[thread overview]
Message-ID: <2E74F312D6980D459F3A05492BA40F8DE4D779@clue.transas.com> (raw)

Hi,

This patch temporarily solve problem with loose arches in gdb 
(set/show architecture command).

Andrey Volkov

2002-05-28  Andrey Volkov  <avolkov@transas.com>

    * cpu-h8300.c : Make default h8300 machine first in
    machine list.


Index: cpu-h8300.c
===================================================================
RCS file: /cvs/src/src/bfd/cpu-h8300.c,v
retrieving revision 1.8
diff -u -r1.8 cpu-h8300.c
--- cpu-h8300.c	4 Apr 2002 14:04:39 -0000	1.8
+++ cpu-h8300.c	28 May 2002 15:20:39 -0000
@@ -97,34 +97,36 @@
     return in;
 }
 
-static const bfd_arch_info_type h8300_info_struct =
+static const bfd_arch_info_type h8300s_info_struct;
+
+static const bfd_arch_info_type h8300h_info_struct =
 {
-  16,				/* 16 bits in a word */
-  16,				/* 16 bits in an address */
+  32,				/* 32 bits in a word */
+  32,				/* 32 bits in an address */
   8,				/* 8 bits in a byte */
   bfd_arch_h8300,
-  bfd_mach_h8300,
-  "h8300",			/* arch_name  */
-  "h8300",			/* printable name */
+  bfd_mach_h8300h,
+  "h8300h",			/* arch_name  */
+  "h8300h",			/* printable name */
   1,
-  true,				/* the default machine */
+  false,			/* the default machine */
   compatible,
   h8300_scan,
 #if 0
   local_bfd_reloc_type_lookup,
 #endif
-  0,
+  &h8300s_info_struct
 };
 
-static const bfd_arch_info_type h8300h_info_struct =
+static const bfd_arch_info_type h8300s_info_struct =
 {
   32,				/* 32 bits in a word */
   32,				/* 32 bits in an address */
   8,				/* 8 bits in a byte */
   bfd_arch_h8300,
-  bfd_mach_h8300h,
-  "h8300h",			/* arch_name  */
-  "h8300h",			/* printable name */
+  bfd_mach_h8300s,
+  "h8300s",			/* arch_name  */
+  "h8300s",			/* printable name */
   1,
   false,			/* the default machine */
   compatible,
@@ -132,24 +134,26 @@
 #if 0
   local_bfd_reloc_type_lookup,
 #endif
-  &h8300_info_struct,
+  0
 };
 
+/* avolkov: Must be first in list, since this is default */
+
 const bfd_arch_info_type bfd_h8300_arch =
 {
-  32,				/* 32 bits in a word */
-  32,				/* 32 bits in an address */
+  16,				/* 16 bits in a word */
+  16,				/* 16 bits in an address */
   8,				/* 8 bits in a byte */
   bfd_arch_h8300,
-  bfd_mach_h8300s,
-  "h8300s",			/* arch_name  */
-  "h8300s",			/* printable name */
+  bfd_mach_h8300,
+  "h8300",			/* arch_name  */
+  "h8300",			/* printable name */
   1,
-  false,			/* the default machine */
+  true,				/* the default machine */
   compatible,
   h8300_scan,
 #if 0
   local_bfd_reloc_type_lookup,
 #endif
-  &h8300h_info_struct,
+  &h8300h_info_struct
 };
 


             reply	other threads:[~2002-05-28 15:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-28  8:50 Andrew Volkov [this message]
2002-05-28 18:05 ` Alan Modra

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=2E74F312D6980D459F3A05492BA40F8DE4D779@clue.transas.com \
    --to=andrew.volkov@transas.com \
    --cc=ac131313@cygnus.com \
    --cc=amodra@bigpond.net.au \
    --cc=binutils@sources.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