Re: Using C as a back end

Andi Kleen <freitag@alancoxonachip.com>
5 Nov 2000 20:52:12 -0500

          From comp.compilers
Related articles
[27 earlier articles]
Re: Using C as a back end rhyde@cs.ucr.edu (Randall Hyde) (2000-11-01)
Re: Using C as a back end vbdis@aol.com (2000-11-04)
Re: Using C as a back end joachim_d@gmx.de (Joachim Durchholz) (2000-11-04)
Re: Using C as a back end thp@roam-thp2.cs.ucr.edu (Tom Payne) (2000-11-04)
Re: Using C as a back end gneuner@dyn.com (2000-11-04)
Re: Using C as a back end fjh@cs.mu.OZ.AU (2000-11-05)
Re: Using C as a back end freitag@alancoxonachip.com (Andi Kleen) (2000-11-05)
Re: Using C as a back end christl@rosalind.fmi.uni-passau.de (2000-11-05)
| List of all articles for this month |
From: Andi Kleen <freitag@alancoxonachip.com>
Newsgroups: comp.compilers
Date: 5 Nov 2000 20:52:12 -0500
Organization: SuSE GmbH, Nuernberg, Germany
References: 00-10-148 00-10-164 00-10-205 00-10-234 00-11-016
Keywords: C, performance

Randall Hyde <rhyde@cs.ucr.edu> writes:


> BTW, even if you turn optimization off, most C++ compilers are still
> slower than most Pascal compilers. So my guess is that the
> single-pass design of Pascal is a large contributing factor.


C can be as well compiled in a single pass as Pascal. What does make
you think it cannot ? Admittedly one pass linking of C is a bit more
complicated than TP units, but it is still possible. Most C compilers
and linkers do not do it, but that has other reasons (mostly code
quality) Compiling C++ will be probably near always slow, because it
requires very complex algorithms to parse (overload resolution
etc. have a cost) C is fine though and you can write fast parsers/code
generators for it.


-Andi

Post a followup to this message

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