C Fronts

whatis@gnu.ai.mit.edu (Steve Boswell)
Sun, 4 Aug 91 01:49:21 -0400

          From comp.compilers
Related articles
C Fronts whatis@gnu.ai.mit.edu (1991-08-04)
Re: C Fronts MASLOV@VADIK.srcc.msu.su (1991-08-05)
Re: C Fronts MASLOV@VADIK.srcc.msu.su (1991-08-07)
Re: C Fronts kers@hplb.hpl.hp.com (Chris Dollin) (1991-08-08)
Re: C Fronts henry@zoo.toronto.edu (1991-08-09)
| List of all articles for this month |
Newsgroups: comp.compilers
From: whatis@gnu.ai.mit.edu (Steve Boswell)
Keywords: C, C++, optimize
Organization: Compilers Central
Date: Sun, 4 Aug 91 01:49:21 -0400

I know of a few languages that are implemented as C fronts (C++, Eiffel,
and Kyoto Common Lisp, to name a few.) C++ generates C code that looks like
C code, while Kyoto Common Lisp generates C code that looks like assembly
langage (i.e. all branches are GOTOs, one very simple operation per line,
etc.) Which leads to better, more optimal compiled code? Have there been
any studies on this?


Steve Boswell
whatis@ucsd.edu
whatis@gnu.ai.mit.edu
[My guess would be that in most cases it doesn't make much difference, though
I've no data to back it up. Most C compilers that I've seen turn higher
level control structures into gotos and then rediscover the loops, since they
have to be prepared for gotos in the user code. -John]
--

Post a followup to this message

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