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: Per Bothner <per at bothner dot com>
- Date: 30 May 2001 18:57:14 -0700
- Cc: gcc at gcc dot gnu dot org
- References: <3B156B14.11A07A4A@apple.com>
Stan Shebs <firstname.lastname@example.org> writes:
> 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.
I don't see how this can be of any use until/unless you integrate the
assembler into cc1, like we've already done for cpp.
Ideally, you'd want to generate binary code directly from rtl,
rather than generating and then parsing assembly code, but a
useful intermediate step may be to go via text, but write the
assembly text to an internal buffer rather than a file.