Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Masaki Muranaka <monaka@monami-software.com>
To: DJ Delorie <dj@redhat.com>
Cc: nickc@redhat.com,  drow@false.org,  gdb-patches@sourceware.org,
	 binutils@sourceware.org
Subject: Re: Can't set architecture to m32c on m32c-elf-gdb.
Date: Fri, 08 Jan 2010 00:02:00 -0000	[thread overview]
Message-ID: <55B67174-01F1-4A30-B65B-32A10B0EC7EB@monami-software.com> (raw)
In-Reply-To: <201001072244.o07Mintk025541@greed.delorie.com>

Hello DJ,

Yes some series cores are already shipped it and some are still planning.
I didn't say R32C is same as M32C. But I think their register sets
and periherals are quite similar.
And Renesas says R32C is the high end model of M16C/M32C series, right?

I agree RX is completely different opcode/registers from M16C family.
("RX is a step up from R32C. " is similar to "SH-1/2 is a step up from H8")
So I have no view about RX supports on GNU chains.

Thanks,

On 2010/01/08, at 7:44, DJ Delorie wrote:

> 
>> Renesas is planning to ship R32C series.
> 
> They're already shipping it.  It's as different from M32C as M32C is
> from M16C (m16c/60 at least) - no opcode compatibility at all, aside
> from a "passing resemblance" at the asm syntax level.
> 
> M16C vs R8C is much closer; they differ only in two opcodes.  M16C/80
> vs M32C/80 have the same architecture, but m32c has more opcodes.
> 
> RX is a step up from R32C.  Same peripherals, basically, but
> completely different opcodes and register set.
> 



--
Masaki Muranaka
Monami software



  reply	other threads:[~2010-01-08  0:02 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 [this message]
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=55B67174-01F1-4A30-B65B-32A10B0EC7EB@monami-software.com \
    --to=monaka@monami-software.com \
    --cc=binutils@sourceware.org \
    --cc=dj@redhat.com \
    --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