From: fche@redhat.com (Frank Ch. Eigler)
To: Miles Bader <miles@gnu.org>
Cc: gcc@gcc.gnu.org, cgen@sources.redhat.com
Subject: Re: cgen?
Date: Mon, 07 Feb 2005 17:26:00 -0000 [thread overview]
Message-ID: <y0mk6pkz6c7.fsf@toenail.toronto.redhat.com> (raw)
In-Reply-To: <buoacqgq3d1.fsf@mctpc71.ucom.lsi.nec.co.jp>
Miles Bader <miles@lsi.nec.co.jp> writes:
> I'm going to write GNU toolchain support (binutils/gas/gcc) for a
> new micro-controller processor arch, and I'd like to know if it's
> recommended these days to use "cgen" or not for the binutils/gas
> bits, as opposed to just rolling everything by hand. [...]
This is not very relevant to gcc, in that cgen has no (public)
gcc-related porting backend. It helps build assemblers and
simulators. It is pretty stable and has a user base (including
various Red Hat porting contracts).
- FChE
parent reply other threads:[~2005-02-07 17:26 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <buoacqgq3d1.fsf@mctpc71.ucom.lsi.nec.co.jp>]
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=y0mk6pkz6c7.fsf@toenail.toronto.redhat.com \
--to=fche@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=miles@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).