Constant pool optimization

[Joel Jones]

>Hello.
>
>Looking at memory profile made by per-method basis,
>I was impressed how mach of memory takes constant
>pool.
>
>I my case that was 530 kb!
>
>I think, there is one possible quick improvement.
>since all CONSTANT_Utf8 constants are not used
>directly, we may simply remove them, after
>class file parsing.

I haven't looked at kaffe in detail to answer this question, but it seems
that supporting the reflection API requires a good deal of this information
be available.  If strings are interned on a global basis, very little can
be removed, if my thinking is correct.

Joel Jones
jjones at uiuc.edu