From: Masaki Muranaka <monaka@monami-software.com>
To: gdb-patches@sourceware.org, binutils@sourceware.org
Subject: Can't set architecture to m32c on m32c-elf-gdb.
Date: Wed, 03 Dec 2008 09:17:00 -0000 [thread overview]
Message-ID: <DD44C478-4E49-4C47-98AB-06DDD086DC40@monami-software.com> (raw)
Hello,
I couldn't set architecture m16c to m32c on the HEAD revision of gdb,
I think it is caused by definition in bfd/cpu-m32c.c but I'm not certain.
Any comments appreciated.
Thanks.
Index: cpu-m32c.c
===================================================================
RCS file: /cvs/src/src/bfd/cpu-m32c.c,v
retrieving revision 1.3
diff -u -p -r1.3 cpu-m32c.c
--- cpu-m32c.c 3 Jul 2007 14:26:40 -0000 1.3
+++ cpu-m32c.c 3 Dec 2008 09:07:51 -0000
@@ -47,7 +47,7 @@ const bfd_arch_info_type bfd_m32c_arch =
8, /* Bits per byte. */
bfd_arch_m32c, /* Architecture. */
bfd_mach_m16c, /* Machine. */
- "m32c", /* Architecture name. */
+ "m16c", /* Architecture name. */
"m16c", /* Printable name. */
4, /* Section align power. */
TRUE, /* The default ? */
--
Masaki Muranaka
Monami Software
next reply other threads:[~2008-12-03 9:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 9:17 Masaki Muranaka [this message]
2008-12-03 14:08 ` Daniel Jacobowitz
2008-12-04 1:04 ` Masaki Muranaka
2008-12-04 4:27 ` Daniel Jacobowitz
2008-12-04 6:48 ` Masaki Muranaka
2008-12-04 13:13 ` Daniel Jacobowitz
2008-12-04 14:22 ` Pedro Alves
2008-12-05 0:29 ` Masaki Muranaka
2009-12-28 2:32 ` Masaki Muranaka
2009-12-31 12:22 ` Nick Clifton
2010-01-03 0:00 ` Masaki Muranaka
2010-01-06 8:18 ` [patch] " Masaki Muranaka
2010-01-06 15:17 ` Nick Clifton
2010-01-06 23:24 ` Masaki Muranaka
2010-01-07 15:54 ` Nick Clifton
2010-01-07 22:38 ` Masaki Muranaka
2010-01-07 22:45 ` DJ Delorie
2010-01-08 0:02 ` Masaki Muranaka
2010-01-08 0:07 ` DJ Delorie
2010-01-08 0:45 ` Masaki Muranaka
2010-01-08 11:40 ` Nick Clifton
2010-01-12 0:04 ` Masaki Muranaka
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=DD44C478-4E49-4C47-98AB-06DDD086DC40@monami-software.com \
--to=monaka@monami-software.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@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