This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: ANSIfy cp/parser.c
- From: Mark Mitchell <mark at codesourcery dot com>
- To: Gabriel Dos Reis <gdr at integrable-solutions dot net>, "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>
- Cc: "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>, "neil at daikokuya dot co dot uk" <neil at daikokuya dot co dot uk>, "neroden at twcny dot rr dot com" <neroden at twcny dot rr dot com>, "zack at codesourcery dot com" <zack at codesourcery dot com>
- Date: Thu, 09 Jan 2003 08:02:38 -0800
- Subject: Re: ANSIfy cp/parser.c
At this point, we need first to consolidate the great work done by
Mark, resolve regressions, pending issues. Since the C front-end is
so crucial, I would suggest we don't do it in the hurry. That does
not mean I don't trust Zack's skills -- that has nothing to do with
that.
I tend to agree. I'm sure there are still bugs in the new parser, and
adding C support will only increase that.
The path to follow, in my opinion, is to implement C support in the
new parser, and C support in the C++ front-end, while still
preserving the C front end.
I don't think the big win in eventually converting the C++ front end to
be a combined C/C++ front end will be performance -- it will be
elimination of many thousands of lines of code, and numerous
inconsistencies between the front ends. It will also make it much
easier to support C99 features in C++, and use some parts of the
C++ front end (like templates and/or overloading) to implement things
like Altivec and generic match support.
People are right to be concerned about the performance impact, and we'll
need to speed up the C++ front end a good bit. Fortunately, this is
going to be one of our major areas of focus, now that the new parser
is (mostly) out of the way.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com