Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Masaki MURANAKA <monaka@monami-software.com>
To: gdb-patches@sourceware.org
Subject: Re: [patch] HR5000 target
Date: Mon, 03 Apr 2006 03:35:00 -0000	[thread overview]
Message-ID: <CBEE85E6-E025-4DCB-81AE-389A10E833FB@monami-software.com> (raw)
In-Reply-To: <20060403031347.GA27402@nevyn.them.org>


On 2006/04/03, at 12:13, Daniel Jacobowitz wrote:
> - Patches to config.sub should not be sent here.  See the top-level
> MAINTAINERS file; I believe it's config-patches@gnu.org.

Thanks. I'll resend there.

> - Why does this need its own target triplet?  Can't you use a normal
> mips-elf or mips64-elf toolchain for this target?

Often it use special libraries/startups.
And the another version of MIPS core chip is also available.
Target board has more than 2 CPUs (MIPS core but the different
version, like 5kf and 4kc).
It will be confused if we reuse mips*-elf target.

--
Masaki Muranaka
Monami software



      reply	other threads:[~2006-04-03  3:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-03  2:56 Masaki MURANAKA
2006-04-03  3:13 ` Daniel Jacobowitz
2006-04-03  3:35   ` 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=CBEE85E6-E025-4DCB-81AE-389A10E833FB@monami-software.com \
    --to=monaka@monami-software.com \
    --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