From: "Galit Heller" <Galit.Heller@nsc.com>
To: johan.rydberg@netinsight.se
Cc: cgen@sources.redhat.com
Subject: HOWTO on porting GNU development tools using CGEN
Date: Sun, 19 Oct 2003 13:47:00 -0000 [thread overview]
Message-ID: <3F9295E4.E66AF5EF@nsc.com> (raw)
Hi,
I am considering using cgen to port GNU binutils to National Semiconductor's
CompactRISC microprocessors. While searching for information I saw
references to the FAQ at http://sources.redhat.com/fom-serv/cgen/cache/1.html,
which does not seem to inlude much.
However, the "howto" described in this almost 2 year old email would be
very helpful. Does it exist, and if so, where could I find it ?
Thanks in advance,
Galit.
--------------------------------------------------------------------------
On Mon, Dec 04, 2000 at 19:10:16PM +0100, Johan Rydberg wrote:
> "Frank Ch. Eigler" wrote:
> > On Mon, Dec 04, 2000 at 04:20:56PM +0100, Johan Rydberg wrote:
> > : Since I have started porting the GNU development tools using CGEN
> > : I have decided to write a small document describing the steps that
> > : you have to go through to do this. Could there be any public interest
> > : is a document of this type?
> >
> > Definitely.
> >
> > One could develop it inside cgen/doc, or on the CGEN Faq-O-Matic page
> > at <http://sources.redhat.com/fom/cgen/> which is empty right now.
>
> Yes.
>
> Right now, fragments of the document is in the CVS-repository for the
> OpenRISC project (at http://openrisc.sourceforge.net/). Maybe we sould
> move it to the sourceware repository?
> If we should move it to the official repository, maybe it's best if I
> removed all references to my port, since I don't see it to be included
> in the standard releases of GNU binutils or CGEN in the near future.
--------------------------------------------------------------------------
reply other threads:[~2003-10-19 13:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3F9295E4.E66AF5EF@nsc.com \
--to=galit.heller@nsc.com \
--cc=cgen@sources.redhat.com \
--cc=johan.rydberg@netinsight.se \
/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).