From: Masaki Muranaka <monaka@monami-software.com>
To: Nick Clifton <nickc@redhat.com>
Cc: Daniel Jacobowitz <drow@false.org>,
gdb-patches@sourceware.org, binutils@sourceware.org
Subject: Re: Can't set architecture to m32c on m32c-elf-gdb.
Date: Tue, 12 Jan 2010 00:04:00 -0000 [thread overview]
Message-ID: <23AFDDF7-E1CC-4714-9AE1-C391AAC92D8F@monami-software.com> (raw)
In-Reply-To: <4B4719A5.6020609@redhat.com>
Hello Nick,
Ok. It might only has to think at that time about R32C.
Thanks
On 2010/01/08, at 20:40, Nick Clifton wrote:
> Hi Masaki,
>
>> Hello Nick,
>> Though I've not tried your patch yet, it also will works fine.
>> But I feel my patch is better.
>> Renesas is planning to ship R32C series. They have a lot of extensions but basically based on M32C.
>> R32C aims automovice areas, so it's possible they have some custom variations.
>> I think it's better to specify architecture by printable name like cpu-arm.c
>
> But that is what my patch does. It fixes the scanning code in the bfd library so that when the user enters:
>
> set architecture m32c
>
> in gdb it will correctly locate the m32c architecture and not the m16c architecture as it was doing previously.
>
> Cheers
> Nick
>
prev parent reply other threads:[~2010-01-12 0:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 9:17 Masaki Muranaka
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 [this message]
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=23AFDDF7-E1CC-4714-9AE1-C391AAC92D8F@monami-software.com \
--to=monaka@monami-software.com \
--cc=binutils@sourceware.org \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=nickc@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