This is the mail archive of the
mailing list for the GCC project.
Re: How would *you* use an intern?
- To: Per Bothner <per at bothner dot com>
- Subject: Re: How would *you* use an intern?
- From: Michael Meissner <meissner at cygnus dot com>
- Date: Wed, 30 May 2001 23:25:31 -0400
- Cc: Stan Shebs <shebs at apple dot com>, gcc at gcc dot gnu dot org
- References: <3B156B14.11A07A4A@apple.com> <email@example.com>
On Wed, May 30, 2001 at 06:57:14PM -0700, Per Bothner wrote:
> 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.
I suspect rewriting all of GCC to use binary instead of encoded text strings
will be quite some undertaking. Even so, embedded asm statements mean you
still have to have the text based assembler lurking in the wings, and
-save-temps must continue to work.
Michael Meissner, Red Hat, Inc. (GCC group)
PMB 198, 174 Littleton Road #3, Westford, Massachusetts 01886, USA
Work: email@example.com phone: +1 978-486-9304
Non-work: firstname.lastname@example.org fax: +1 978-692-4482