[Bug objc++/31134] [4.3 Regression] Objective-C++ has ran into the tree number limit

["dave at hiauly1 dot hia dot nrc dot ca" <gcc-bugzilla at gcc dot gnu dot org>]

------- Comment #5 from dave at hiauly1 dot hia dot nrc dot ca  2007-03-12 00:55 -------
Subject: Re:  [4.3 Regression] Objective-C++ has ran into the tree number limit

> > Don't like to name people, but I suppose this patch should be reverted:
> 
> Please, please, don't do that! Instead, let's solve the real issue with the
> tree-codes limit once and for all, because sooner or later we have to do that
> anyway (as Rth, among others, also maintained time ago, in the occasion of the
> GOMP additions)

I recognize that the patch contains a very significant body of work.
I also realize that the tree code limit needs fixing.  However,
that may require a significant increase in memory for trees.  That's
why I added the comment.

It's not fair to trade one feature for another (variadic templates
for obj-c++).

There's been no discussion on the impact of fixing the tree code limit.
I note that a 15% compile time memory usage regression,
<http://gcc.gnu.org/ml/gcc-patches/2007-03/msg00652.html>,
would be considered a release blocker.

The patch was obviously not fully tested, or the problem was overlooked.
As a backend maintainer, I've seen build and check times grow substantially
with every new release.  So, I'm highly suspicious of the process used
to introduce major new features.  The tree code limit should have been
fixed first.

Dave


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31134