This is the mail archive of the
mailing list for the GCC project.
Re: How would *you* use an intern?
- To: Stan Shebs <shebs at apple dot com>
- Subject: Re: How would *you* use an intern?
- From: Fergus Henderson <fjh at cs dot mu dot oz dot au>
- Date: Thu, 31 May 2001 13:20:11 +1000
- Cc: gcc at gcc dot gnu dot org
- References: <3B156B14.11A07A4A@apple.com>
On 30-May-2001, Stan Shebs <email@example.com> wrote:
> A more radical change that we were thinking about was to make GCC
> reentrant in some fashion, so you could have multiple incremental
> compiles going on behind the scenes, but not be thrashing the
> machine by bringing up cc1 executables up and down all the time.
> So GCC becomes a sort of compile server, taking big and little
> compilation tasks from the IDE. To do something like that, you'd
> want to gather up globals into some sort of compile state that
> could be per-thread.
An intermediate step towards that which might perhaps get some of the
benefit would be to have `cc1 --server' just do its initialization and
then fork() for each compilation request from the IDE (or from `gcc',
for that matter). That would at least save an exec() for each compilation
But I'm not sure how much you'd actually save with this approach.
Fergus Henderson <firstname.lastname@example.org> | "I have always known that the pursuit
| of excellence is a lethal habit"
WWW: <http://www.cs.mu.oz.au/~fjh> | -- the last words of T. S. Garp.