I just noticed that the Java frontend has ARG_FINAL_P, which uses a
bit in the TREE_LIST node that is pointed to from TYPE_ARG_TYPES.
It's only used in the Java source front-end, which is going away.
We could figure out an alternative, but I'm not sure it's worthwhile.
As a stop-gap, you could
Hi Mark,
Yes. Kazu, I'd suggest you just ignore Java; you can still get
proof-of-concept for tree-trimming without Java. The ECJ changes are
going to be massive, and they're going to go in before we get our stuff
ready to go in, so dealing with Java now is probably a waste of time;
we'll have
Hi Tom,
Kazu> I just noticed that the Java frontend has ARG_FINAL_P, which uses a
Kazu> bit in the TREE_LIST node that is pointed to from TYPE_ARG_TYPES.
Kazu> I am wondering if there is any way we could move this bit elsewhere.
On the gcj-eclipse branch the code that uses ARG_FINAL_P is actua
Tom Tromey wrote:
>> "Kazu" == Kazu Hirata <[EMAIL PROTECTED]> writes:
>
> Kazu> I just noticed that the Java frontend has ARG_FINAL_P, which uses a
> Kazu> bit in the TREE_LIST node that is pointed to from TYPE_ARG_TYPES.
>
> Kazu> I am wondering if there is any way we could move this bit el
> "Kazu" == Kazu Hirata <[EMAIL PROTECTED]> writes:
Kazu> I just noticed that the Java frontend has ARG_FINAL_P, which uses a
Kazu> bit in the TREE_LIST node that is pointed to from TYPE_ARG_TYPES.
Kazu> I am wondering if there is any way we could move this bit elsewhere.
On the gcj-eclipse
Hi,
I'm planning to change TYPE_ARG_TYPES to use TREE_VEC instead of
TREE_LIST for compact representation.
I just noticed that the Java frontend has ARG_FINAL_P, which uses a
bit in the TREE_LIST node that is pointed to from TYPE_ARG_TYPES.
I am wondering if there is any way we could move this b
