Using C as a back end

"Pred." <predictor@my-deja.com>
19 Oct 2000 14:39:24 -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)
[28 later articles]
| List of all articles for this month |
From: "Pred." <predictor@my-deja.com>
Newsgroups: comp.compilers
Date: 19 Oct 2000 14:39:24 -0400
Organization: Deja.com - Before you buy.
Keywords: translator, question, comment

Hi!


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?


I see the following pros and cons:


PROS:
1. I don't have to learn about / write code generators for the various
targets
2. "Tried'n'true" back end
3. Shorter time-to-market


CONS:
1. Slower compilation (scan + parse occurs twice)
2. No control over new versions of the back end


Have there been any work on good ways to transform one language into C
source?


Any comments?
--
Thanks
[Lots of compilers use C as a back end, including the original Eiffel and
C++ compilers. -John]

Post a followup to this message

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