On 11/21/14 11:48, Andrew MacLeod wrote:
There are a few issues, of course :-)
The biggest issue is what to do with fields which can be either a type
or a tree... ie TREE_VALUE() of a TREE_LIST can be a type, as can a
TREE_VEC element or a DECL_CONTEXT. I think the DECL_INITIAL field is
overloaded and can sometimes be a type, and this was recently introduced
to TARGET_STATIC_CHAIN. I suspect the compilation process will identify
others.
Well, we rip them apart, naturally :-) The exact mechanism may differ
from one instance to the next.
In the specific case of the TARGET_STATIC_CHAIN changes, I think we can
just split that into two parameters, one of which will be a DECL, the
other a TYPE (and one of which will always be NULL).
I'd think these changes ought to move forward independently of your work
as they're, IMHO independent cleanups.
Jeff
