From: Ben Elliston <bje@wasabisystems.com>
To: Ralph Escherich <esche@mobilesmartsinc.com>
Cc: cgen@sources.redhat.com
Subject: Re: binutils porting to new CPU
Date: Fri, 31 Oct 2003 04:25:00 -0000 [thread overview]
Message-ID: <87wuamghjz.fsf@wasabisystems.com> (raw)
In-Reply-To: <200310300848.55978.esche@mobilesmartsinc.com>
Ralph Escherich <esche@mobilesmartsinc.com> writes:
> No, I'm using binutils-2.14. For cgen I'm using the latest CVS snap.
> I couldn't get the scheme code going with release 1.0.
You should use CVS binutils if you're using CVS cgen.
> Which CPU port would be an easy one to get started with?
fr30 is probably a nice case.
Ben
prev parent reply other threads:[~2003-10-31 4:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-29 2:20 Ralph Escherich
2003-10-29 2:48 ` Frank Ch. Eigler
2003-10-29 16:37 ` Ralph Escherich
2003-10-29 16:50 ` Frank Ch. Eigler
2003-10-30 0:29 ` Ralph Escherich
2003-10-30 1:53 ` Ben Elliston
2003-10-30 5:46 ` Ralph Escherich
2003-10-30 6:43 ` Ben Elliston
2003-10-30 16:47 ` Ralph Escherich
2003-10-31 4:25 ` Ben Elliston [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=87wuamghjz.fsf@wasabisystems.com \
--to=bje@wasabisystems.com \
--cc=cgen@sources.redhat.com \
--cc=esche@mobilesmartsinc.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).