Re: Putting C++ code into gcc front end

["Gareth Pearce" <tilps at hotmail dot com>]

Is a random nobody I think i'll contribute how I think compiling gcc should
work.

basic pattern
stage 0 - compiles a C compiler capable of compiling the C frontend/backend
using minimalistic assumptions about input.
stage 1 - compile a C compiler assuming a reasonable standard - such
something like as ISO C90
stage 2 - compile a C compiler assuming gcc compatible parameters/flags
stage 2a - compile things which use C using stage 2- same standard (or gnu
extensions?)
stage 2b - compile things dependent on 2a - using stage 2a
... - compile those dependent on previous stage - using previous stage
stage 3 - as stage 2
stage 3a - see 2a but using stage 3 compiler
...
stage 4 - compare stage 2 and stage 3
stage 5 - compare 2a 3a - 2b 3b ...
stage 6 - run testsuite on either stage 2, 2a... or 3, 3a... (latest one
available by default)

make
- runs stage 3, 3a... assuming system compiler as input to stage 3

make check
- runs stage 6

make antique
- runs stage 0 - using system compiler

make quickstrap
- runs stage 1 using system compiler
- then stage 3, 3a... using stage 1

make bootstrap
- runs stage 1 using system
- stage 2 using stage 1
- stage 3 using stage 2
- stage 4
- stage 3a, b ...

make bootstrap-check - depends on make bootstrap
- stage 2a, b ... (maybe make b onwards optional here)
- stage 5

okay i'm done, i'll go back to my dream world now...

Gareth