Re: gcc versus cfront (AT&T)

sastdr@unx.sas.com (Thomas David Rivers)
Fri, 11 Nov 1994 16:32:19 GMT

          From comp.compilers

Related articles
gcc versus cfront (AT&T) jho@imada.ou.dk (1994-11-09)
Re: gcc versus cfront (AT&T) jbuck@Synopsys.COM (1994-11-10)
Re: gcc versus cfront (AT&T) sastdr@unx.sas.com (1994-11-11)
| List of all articles for this month |

Newsgroups: comp.compilers
From: sastdr@unx.sas.com (Thomas David Rivers)
Keywords: C++
Organization: SAS Institute Inc.
References: 94-11-037 94-11-070
Date: Fri, 11 Nov 1994 16:32:19 GMT

jho@imada.ou.dk (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
identifiers, etc...)


  We basically view the 'C' output as a higher-level intermediate form.


- Dave Rivers -
--


Post a followup to this message

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