We're out of tree codes; now what?

David Edelsohn dje@watson.ibm.com
Wed Mar 14 17:09:00 GMT 2007

>>>>> Diego Novillo writes:

> There was some other comment in this thread about tuples helping this.
> They will not.  Tuples are not going to remove existing codes, in fact
> they are going to be separate data structures at some point.  ATM, all
> tuples are doing is adding one new tree code (which right now is
> reserved by GIMPLE_MODIFY_STMT).

	I was under the impression that Tuples would help with the tree
codes because of some comments during the Tuples RFC about extending
tree_code to 16 bits as part of the Tuples conversion:


"We certainly have a lot of padding in tree_base.  I think a 16 bit code
is a good idea."

I inferred that the Tuples conversion was creating a more efficient
representation for which 16 bit tree_code would be practical.


More information about the Gcc-patches mailing list