Re: Using C as a back end

"Conor O'Neill" <ONeillCJ@logica.com>
26 Oct 2000 02:46:24 -0400

          From comp.compilers
Related articles
[8 earlier articles]
Re: Using C as a back end lazzaro@cs.berkeley.edu (2000-10-23)
Re: Using C as a back end predictor@my-deja.com (Pred.) (2000-10-23)
Re: Using C as a back end predictor@my-deja.com (Pred.) (2000-10-23)
Re: Using C as a back end sweeks@my-deja.com (Stephen T. Weeks) (2000-10-23)
Re: Using C as a back end jaidi@fos.ubd.edu.bn (Pg Nor Jaidi Pg Tuah) (2000-10-26)
Re: Using C as a back end predictor@my-deja.com (Pred.) (2000-10-26)
Re: Using C as a back end ONeillCJ@logica.com (Conor O'Neill) (2000-10-26)
Re: Using C as a back end kst@cts.com (Keith Thompson) (2000-10-26)
Re: Using C as a back end jacob@jacob.remcomp.fr (jacob navia) (2000-10-26)
Re: Using C as a back end nr@labrador.eecs.harvard.edu (2000-10-31)
Re: Using C as a back end sweeks@my-deja.com (Stephen T. Weeks) (2000-10-31)
Re: Using C as a back end zs@ender.cs.mu.oz.au (2000-10-31)
Re: Using C as a back end thp@cs.ucr.edu (Tom Payne) (2000-10-31)
[14 later articles]
| List of all articles for this month |
From: "Conor O'Neill" <ONeillCJ@logica.com>
Newsgroups: comp.compilers
Date: 26 Oct 2000 02:46:24 -0400
Organization: Speaking for myself
References: 00-10-148 00-10-164
Keywords: performance

Joachim Durchholz <joachim_d@gmx.de> writes
>[Actually, in many compilers the scanner is the slowest part because
>it's the only thing that has to look at every character in the source
>file. -John]


I thought that the scanner is the slowest part, because the scanner
looks at every character in the headers multiple times, once for each
compilation module.


Pre compiled headers presumably speed this up considerably, but the
systems I use don't have them.
--
Conor O'Neill, Bristol, UK

Post a followup to this message

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