I see now. Thanks for clarification.
As we are using "merged cp" inside DRLVM, can we just not take care of
exceeding 16-bit boundary and keep cp indexes as 32-bit values?
Or we export this information somewhere...?
Pavel Pervov wrote:
In current codebase "merged" constant pool will cause many problems for
interpreter and one problem for JIT - if call to "throw_linking_exception"
stub is compiled into some method. As you may remember it contains
immediate
value of constant pool index of a referenced class.
Also, Mikhail noted new functionality currently being implemented - lazy
resolution. It will also be heavily affected with constant pool merging.
Regards,
Pavel.
