This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Putting C++ code into gcc front end
- From: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- To: Zack Weinberg <zack at codesourcery dot com>
- Cc: tromey at redhat dot com, GCC Hackers <gcc at gcc dot gnu dot org>
- Date: 04 Mar 2003 07:37:39 +0100
- Subject: Re: Putting C++ code into gcc front end
- Organization: Integrable Solutions
- References: <87of4rnc0c.fsf@fleche.redhat.com><877kbf3btx.fsf@egil.codesourcery.com>
Zack Weinberg <zack at codesourcery dot com> writes:
[...]
| On the one hand I think that putting C++ into any part of the compiler
| is a bad idea, because it will make bootstrapping more difficult --
| even in this limited situation where C++ appears in none of the C
| front end, the C++ front end, or the language-independent modules.
| The C++ front end cannot be built in stage 1 due to its use of GNU
| extensions to C; thus, starting from nothing but a non-GNU C compiler
| one would have to do a four stage bootstrap. If libstdc++ has to get
| involved (and it probably does, at least for the runtime support
| routines) it's even worse
I don't think this is much worse than the current situation where one
needs to have g++ + libstdc++-v3 built if one wants Java.
And bootstrap for C++ front-end is currently an oxymoron: it is just a
bootstrap for the C compiler.
-- Gaby