This is the mail archive of the
mailing list for the GCC project.
Re: PATCH C++: speed up templates
- From: Matt Austern <austern at apple dot com>
- To: Mark Mitchell <mark at codesourcery dot com>
- Cc: Ziemowit Laski <zlaski at apple dot com>, Mike Stump <mrs at apple dot com>, "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>
- Date: Wed, 19 Feb 2003 10:52:19 -0800
- Subject: Re: PATCH C++: speed up templates
On Tuesday, February 18, 2003, at 01:08 PM, Mark Mitchell wrote:
--On Tuesday, February 18, 2003 12:27:42 PM -0800 Matt Austern
<austern at apple dot com> wrote:
Is that true even in 3.3? Remember, it's the 3.3 release branch
found the regression.
No, it's not going to be true for 3.3 -- which is why I approved
Mike's patch there. :-)
Suppose we take a more radical approach, and just back out your patch
entirely from the 3.3 release branch. What would be the consequences?
At a general level I understand what this means is that a certain class
of template-related bugs won't get fixed in 3.3 and the fix will have
to wait until 3.4. How important are those bugs, considering (a) all
the other template-related bugs that can't be fixed without the new
parser; and (b) the performance regression that this bug fix caused?