From: Michael Eager <eager@eagercon.com>
To: binutils@sourceware.org, gdb@sourceware.org
Subject: Add define for PowerPC 405 to bfd
Date: Fri, 26 Jun 2009 17:32:00 -0000 [thread overview]
Message-ID: <4A450609.3040009@eagercon.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 296 bytes --]
This adds a definition for PowerPC 405. I only patched
bfd-in2.h rather than regenerate it.
2009-06-26 Michael Eager <eager@eagercon.com>
* bfd/archures.c: Add bfd_mach_ppc_405
* bfd/bfd-in2.h: Same.
--
Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
[-- Attachment #2: bfd.patch --]
[-- Type: text/plain, Size: 1045 bytes --]
Index: archures.c
===================================================================
RCS file: /cvs/src/src/bfd/archures.c,v
retrieving revision 1.139
diff -u -r1.139 archures.c
--- archures.c 26 May 2009 14:12:02 -0000 1.139
+++ archures.c 26 Jun 2009 17:25:47 -0000
@@ -210,6 +210,7 @@
.#define bfd_mach_ppc64 64
.#define bfd_mach_ppc_403 403
.#define bfd_mach_ppc_403gc 4030
+.#define bfd_mach_ppc_405 405
.#define bfd_mach_ppc_505 505
.#define bfd_mach_ppc_601 601
.#define bfd_mach_ppc_602 602
Index: bfd-in2.h
===================================================================
RCS file: /cvs/src/src/bfd/bfd-in2.h,v
retrieving revision 1.485
diff -u -r1.485 bfd-in2.h
--- bfd-in2.h 12 Jun 2009 09:15:45 -0000 1.485
+++ bfd-in2.h 26 Jun 2009 17:25:52 -0000
@@ -1857,6 +1857,7 @@
#define bfd_mach_ppc64 64
#define bfd_mach_ppc_403 403
#define bfd_mach_ppc_403gc 4030
+#define bfd_mach_ppc_405 405
#define bfd_mach_ppc_505 505
#define bfd_mach_ppc_601 601
#define bfd_mach_ppc_602 602
next reply other threads:[~2009-06-26 17:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 17:32 Michael Eager [this message]
2009-06-29 23:40 ` Alan Modra
2009-06-29 23:56 ` Michael Eager
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=4A450609.3040009@eagercon.com \
--to=eager@eagercon.com \
--cc=binutils@sourceware.org \
--cc=gdb@sourceware.org \
/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