Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: ColdFire/fido support
Date: Sat, 30 Jun 2007 15:47:00 -0000	[thread overview]
Message-ID: <je7ipltpym.fsf@sykes.suse.de> (raw)
In-Reply-To: <200705281542.47676.vladimir@codesourcery.com> (Vladimir Prus's 	message of "Mon\, 28 May 2007 15\:42\:47 +0400")

Vladimir Prus <vladimir@codesourcery.com> writes:

> +  /* The mechanism for returning floating values from function
> +     and the type of long double depend on whether we're
> +     on ColdFire or standard m68k. */
> +
> +  if (info.bfd_arch_info)
> +    {
> +      const bfd_arch_info_type *coldfire_arch = 
> +	bfd_lookup_arch (bfd_arch_m68k, bfd_mach_mcf_isa_a_nodiv);
> +
> +      if (coldfire_arch
> +	  && (*info.bfd_arch_info->compatible) 
> +	  (info.bfd_arch_info, coldfire_arch))
> +	flavour = m68k_coldfire_flavour;
> +    }

This always sets flavour to m68k_coldfire_flavour, since any m68k arch
is always compatible with the generic m68k architecture.

Andreas.

2007-06-30  Andreas Schwab  <schwab@suse.de>

	* m68k-tdep.c (m68k_gdbarch_init): Don't infer coldfire flavour
	from the generic m68k arch.

--- gdb/m68k-tdep.c.~1.120.~	2007-06-19 11:04:57.000000000 +0200
+++ gdb/m68k-tdep.c	2007-06-30 17:26:39.000000000 +0200
@@ -1110,14 +1110,14 @@ m68k_gdbarch_init (struct gdbarch_info i
      and the type of long double depend on whether we're
      on ColdFire or standard m68k. */
 
-  if (info.bfd_arch_info)
+  if (info.bfd_arch_info && info.bfd_arch_info->mach != 0)
     {
       const bfd_arch_info_type *coldfire_arch = 
 	bfd_lookup_arch (bfd_arch_m68k, bfd_mach_mcf_isa_a_nodiv);
 
       if (coldfire_arch
-	  && (*info.bfd_arch_info->compatible) 
-	  (info.bfd_arch_info, coldfire_arch))
+	  && ((*info.bfd_arch_info->compatible) 
+	      (info.bfd_arch_info, coldfire_arch)))
 	flavour = m68k_coldfire_flavour;
     }
   

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."


  parent reply	other threads:[~2007-06-30 15:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-05  9:37 Vladimir Prus
2007-05-05 11:02 ` Andreas Schwab
2007-05-06 11:52   ` Vladimir Prus
2007-05-28 11:43     ` Vladimir Prus
2007-06-05 15:19       ` Daniel Jacobowitz
2007-06-08 10:58         ` Vladimir Prus
2007-06-12 13:38           ` Daniel Jacobowitz
2007-06-15 10:17             ` Vladimir Prus
2007-06-15 14:47               ` Daniel Jacobowitz
2007-06-15 19:05                 ` Vladimir Prus
2007-06-16 10:21                   ` Eli Zaretskii
2007-06-19 16:39                     ` Vladimir Prus
2007-06-19 16:53                       ` Eli Zaretskii
2007-06-19 17:10                         ` Daniel Jacobowitz
2007-06-19 18:00                           ` Eli Zaretskii
2007-06-20  9:14                             ` Vladimir Prus
2007-06-20 18:15                               ` Eli Zaretskii
2007-06-30 15:47       ` Andreas Schwab [this message]
2007-06-30 16:00         ` Daniel Jacobowitz

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=je7ipltpym.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=gdb-patches@sources.redhat.com \
    --cc=vladimir@codesourcery.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