Re: Putting C++ code into gcc front end

[Tom Lord <lord at emf dot net>]

Aside from all the more pressing issues yr dealing with, I think it'd
be a swell idea to work towards maintaining a bootstrap path from raw
iron to GCC that doesn't depend on either old versions of GCC or
proprietary compilers.   And there's actually a potential day-to-day
practical benefit from doing so.

Supposing one does something like:

	forthish -> text/shell-utilish -> tiny fast CC -> GCC

the tiny, fast, GCC (and yes, there are several current candidates for
that stage, though some of the best have problematic licenses) can
have the practical use of being GCC-compatible and relentlessly
trading quality of generated code for raw compilation speed (but with
at least some GNUC extensions).   Why gosh, such a compiler would
likely have some useful IDE applications.

As a side effect, you'd have a permanent, clean, alterntative to
worrying about things like K&R bootstrapping paths and the like.

Ya know?

"but then again, I guess I'm just weird that way",
-t