Re: Using C as a back end

Peter Gammie <peteg@cse.unsw.edu.au>
22 Oct 2000 01:17:50 -0400

          From comp.compilers
Related articles
Using C as a back end predictor@my-deja.com (Pred.) (2000-10-19)
Re: Using C as a back end jim.granville@designtools.co.nz (Jim Granville) (2000-10-22)
Re: Using C as a back end peteg@cse.unsw.edu.au (Peter Gammie) (2000-10-22)
Re: Using C as a back end frido@q-software-solutions.com (Friedrich Dominicus) (2000-10-22)
Re: Using C as a back end joachim_d@gmx.de (Joachim Durchholz) (2000-10-22)
Re: Using C as a back end jacob@jacob.remcomp.fr (jacob navia) (2000-10-22)
Re: Using C as a back end nr@labrador.eecs.harvard.edu (2000-10-22)
Re: Using C as a back end sjmeyer@www.tdl.com (2000-10-23)
Re: Using C as a back end lazzaro@cs.berkeley.edu (2000-10-23)
[26 later articles]
| List of all articles for this month |
From: Peter Gammie <peteg@cse.unsw.edu.au>
Newsgroups: comp.compilers
Date: 22 Oct 2000 01:17:50 -0400
Organization: University of New South Wales
References: 00-10-148
Keywords: C, translator

Take a look at Simon Peyton-Jones et. al.'s work on Haskell -> C
mappings:


http://research.microsoft.com/Users/simonpj/Papers/papers.html


Daniel Diaz's work on wamcc (do a google search), and the Mercury
project are both (basically) Prolog -> C mappings.


The biggest problem with compiling to C is its lack of
expressiveness; almost certainly you'll want to use gcc's extensions
(such as goto), unless your language is already close to C.


For a real challenge, try targetting the JVM. ;-)


cheers
peter


"Pred." wrote:
> I have designed a language for which I'm hoping to create a compiler.
> Since I want a portable solution I was thinking about using a
> retargable C or C++ compiler in the back end along with appropriate
> assembler / linkers. Is this a good solution?

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.