[RFC / Patch] C++/26099 or front-end support to type traits

Mike Stump mrs@apple.com
Tue Mar 13 17:29:00 GMT 2007

On Mar 13, 2007, at 9:31 AM, Paolo Carlini wrote:
>> I object to any more new tree codes, without us first setting a   
>> direction we want to go.
> Yes, I'm certainly going to need *one* tree code, but I can do  
> nothing about that.

If we accept that from contributors, and we want to remain inside the  
255 limit, we are doomed to failure.  Everyone just wants one.  A  
hard line means, absolutely not, no exceptions, not for anyone, at  
any time, for any reason.

I just converted the Objective-C front-end to free up enough tree  
codes so that Objective-C++ can compile again.  I know it can be  
done.  If you want a new tree code, you can convert some other tree  
code into a subcode. pick one one.

For ideas, please see the below patch.  I glanced at the C++ front  
end, I see 8 tree codes (all the tcc_type codes) that you can reclaim  
using the technique below.

For those that want to begin reviewing it, have at it, I'd be  
interested in, do we even want to go in this direction (we don't have  
hard numbers on the compile time costs yet, I don't think)?  If so,  
any better way to do this in the short term?

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: tc.diffs.txt
URL: <http://gcc.gnu.org/pipermail/gcc-patches/attachments/20070313/19fe8fed/attachment.txt>

More information about the Gcc-patches mailing list