|gcc versus cfront (AT&T) firstname.lastname@example.org (1994-11-09)|
|Re: gcc versus cfront (AT&T) jbuck@Synopsys.COM (1994-11-10)|
|Re: gcc versus cfront (AT&T) email@example.com (1994-11-11)|
|From:||firstname.lastname@example.org (Thomas David Rivers)|
|Organization:||SAS Institute Inc.|
|Date:||Fri, 11 Nov 1994 16:32:19 GMT|
email@example.com (Jens H. Ovesen) writes:
>Just one (maybe not so simple to answer) question: What are the pros and
>cons of gcc and cfront from AT&T?
jbuck@Synopsys.COM (Joe Buck) writes:
>... [cfront translates to C which causes performance problems]
The SAS/C C++ compiler on the mainframe produces a 'C' (note the quotes)
file which the SAS/C compiler then translates. This 'C' file is sprinkled
with many interal #pragma's so, is a little more than plain C. Also,
the C++ compiler generates the debugging file which is augmented by
the other phases (for example, code generation decorates offsets of
We basically view the 'C' output as a higher-level intermediate form.
- Dave Rivers -
Return to the
Search the comp.compilers archives again.