From: Joel Sherrill <joel.sherrill@OARcorp.com>
To: Nick Clifton <nickc@cambridge.redhat.com>
Cc: Ivan Guzvinec <ivang@opencores.org>, binutils@sources.redhat.com
Subject: Re: Patch: support for or32 architecture
Date: Wed, 30 Jan 2002 10:28:00 -0000 [thread overview]
Message-ID: <3C57FF82.663F872E@OARcorp.com> (raw)
In-Reply-To: <m3d6zs2knn.fsf@north-pole.nickc.cambridge.redhat.com>
Nick Clifton wrote:
>
> Hi Ivan,
>
> > Added support for or32 architecture (--target=or32-rtems).
>
> Thanks for submitting this. I have had a brief look and it appears
> OK, but I am going to hold off accepting and applying this patch until
> after the 2.12 branch occurs.
Could I plead for this being merged pre-branch? As the target
indicates,
there is an RTEMS port to the or32 which is currently hard for people
to use because the tools require snapshots. This leads to the RTEMS
project supporting non-mainstream release tools for this CPU.
If it is merged, I will add or32-rtems binutils to the standard
set of targets we provide prebuilt binaries for. We provide
GNU/Linux, Cygwin, and Solaris binaries and a FreeBSD ports
package for all *-rtems targets that are in mainstream releases.
If that doesn't sway you, how about a "please pretty please
with sugar on top." :)
> Cheers
> Nick
--
Joel Sherrill, Ph.D. Director of Research & Development
joel@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985
next prev parent reply other threads:[~2002-01-30 17:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-28 12:25 Ivan Guzvinec
2002-01-30 3:24 ` Nick Clifton
2002-01-30 9:36 ` Ivan Guzvinec
2002-01-30 10:28 ` Joel Sherrill [this message]
2002-01-30 11:06 ` Nick Clifton
2002-01-31 9:48 ` Nick Clifton
2002-02-01 4:19 ` Ivan Guzvinec
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=3C57FF82.663F872E@OARcorp.com \
--to=joel.sherrill@oarcorp.com \
--cc=binutils@sources.redhat.com \
--cc=ivang@opencores.org \
--cc=nickc@cambridge.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).