From: Eric Christopher <echristo@redhat.com>
To: Hong Lin <honglin@cs.wisc.edu>
Cc: gcc@gcc.gnu.org
Subject: Re: Using GCC as code generator
Date: Fri, 24 Jan 2003 23:47:00 -0000 [thread overview]
Message-ID: <1043447462.30975.7.camel@ghostwheel.ges.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0301241437360.6343-100000@homer.cs.wisc.edu>
On Fri, 2003-01-24 at 12:50, Hong Lin wrote:
> Hi,
> I am currently exploring the possibility of using gcc backend to generate
> binary code from an intermediate representation. I appreciate very much if
> anyone could point me to any references or give any suggestions. In
> particular, I need to find out the answer for
> 1. Up to dated specification of the intermediate representation that gcc
> uses (tree, RTL)
This is in the documentation available on gcc.gnu.org.
> 2. the way to invoke gcc backend independantly of the frontend
This is not possible, and unlikely necessary for what your aims are.
-eric
--
Strapping on the jetpack...
next prev parent reply other threads:[~2003-01-24 22:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 21:38 Hong Lin
2003-01-24 23:47 ` Eric Christopher [this message]
2003-01-27 21:52 ` Jim Wilson
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=1043447462.30975.7.camel@ghostwheel.ges.redhat.com \
--to=echristo@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=honglin@cs.wisc.edu \
/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).