public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Alexander Aganichev" <AAganichev@hypercom.com>
To: binutils@sourceware.cygnus.com
Subject: bfd patch for backward compatibility with older IEEE objects
Date: Sun, 09 Jul 2000 23:25:00 -0000	[thread overview]
Message-ID: <OF3508BC09.52D0AB08-ONC3256918.0022BDCF@hypercom.com> (raw)

Hi!

The following patch should fix reading older IEEE objects by fresh
binutils. I'm not sure, but it looks like all or a lot of m68k related
cases below the code I've added is useless.

diff -ruNd binutils-000708/bfd/ChangeLog
binutils-000708-hypercom/bfd/ChangeLog
--- binutils-000708/bfd/ChangeLog  Mon Jul 10 09:38:01 2000
+++ binutils-000708-hypercom/bfd/ChangeLog    Mon Jul 10 10:14:02 2000
@@ -1,3 +1,8 @@
+2000-07-10  Alexander Aganichev  <AAganichev@hypercom.com>
+
+    * archures.c (bfd_default_scan): Add set of bfd_mach_ cases for
+    compatibility with older binutils.
+
 2000-07-08  Alan Modra  <alan@linuxcare.com.au>

     * section.c (struct sec): Add id field.  Tidy comment formatting.
diff -ruNd binutils-000708/bfd/archures.c
binutils-000708-hypercom/bfd/archures.c
--- binutils-000708/bfd/archures.c Mon Jul 10 09:38:01 2000
+++ binutils-000708-hypercom/bfd/archures.c   Mon Jul 10 10:15:25 2000
@@ -807,6 +807,18 @@
   switch (number)
     {
       /* FIXME: These are needed to parse IEEE objects.  */
+      /* The following seven case's are here only for compatibility with
+     older binutils (at least IEEE objects from binutils 2.9.1 require
+     these) */
+    case bfd_mach_m68000:
+    case bfd_mach_m68010:
+    case bfd_mach_m68020:
+    case bfd_mach_m68030:
+    case bfd_mach_m68040:
+    case bfd_mach_m68060:
+    case bfd_mach_cpu32:
+      arch = bfd_arch_m68k;
+      break;
     case 68000:
       arch = bfd_arch_m68k;
       number = bfd_mach_m68000;

--
Alexander Aganichev
Software Engineer
Hypercom Europe Limited, Inc.

             reply	other threads:[~2000-07-09 23:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-09 23:25 Alexander Aganichev [this message]
2000-07-10 11:30 Nick Clifton

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=OF3508BC09.52D0AB08-ONC3256918.0022BDCF@hypercom.com \
    --to=aaganichev@hypercom.com \
    --cc=binutils@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).