From: Kazuhio Inaoka <inaoka.kazuhiro@renesas.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Transepose Mitsubishi to Renesas for M32R processor.
Date: Wed, 23 Apr 2003 03:07:00 -0000 [thread overview]
Message-ID: <003801c30942$98ca6b80$2569910a@hoku.renesas.com> (raw)
In-Reply-To: <3EA5CE42.13FCD39E@redhat.com>
> Kazuhio Inaoka wrote:
> >
> > Renesas Technology Corp. is a new semiconductor company, established on
> > April 1st, 2003, as a joint venture between Hitachi, Ltd.(TSE: 6501) and
> > Mitsubishi Electric Corporation(TSE: 6503).
> >
> > M32R Information:
> > http://www.renesas.com/eng/products/mpumcu/32bit/m32r/index.html
> >
> > 2003-04-22 Kazuhiro Inaoka <inaoka dot kazuhiro at renesas dot com>
> > * gdb/m32r-rom.c : Change Mitsubishi to Renesas.
> > gdb/m32r-tdep.c : ditto
> > gdb/config/m32r/m32r.mt : ditto
> > gdb/config/m32r/tm-m32r.h : ditto
> > gdb/doc/gdb.texinfo : ditto
> > gdb/doc/gdb.info-1 : ditto
> > gdb/doc/gdb.info-8 : ditto
> >
>
--------------------------------------------------------------------------
-----
> > Name: gdb-5.3-a.patches
> > gdb-5.3-a.patches Type: unspecified type
(application/octet-stream)
> > Encoding: quoted-printable
>
> In the current source tree, the m32r target has been obsoleted.
> Other than that, I can see no objection to these changes.
Really?
We need gdb for M32R processor from now on.
What can I do about that?
Kazuhiro Inaoka
next prev parent reply other threads:[~2003-04-23 2:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 6:56 Kazuhio Inaoka
2003-04-22 8:20 ` Eli Zaretskii
2003-04-22 8:37 ` Kazuhio Inaoka
2003-04-22 23:20 ` Michael Snyder
2003-04-23 3:07 ` Kazuhio Inaoka [this message]
2003-04-25 2:23 ` Andrew Cagney
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='003801c30942$98ca6b80$2569910a@hoku.renesas.com' \
--to=inaoka.kazuhiro@renesas.com \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@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