invokeinterface handle-walking unimplemented?

[Rémi Forax]

On 05/16/2011 09:48 AM, Christian Thalinger wrote:
> On May 14, 2011, at 6:49 PM, Charles Oliver Nutter wrote:
>> FYI, I assume I'm supposed to see this when I bind an interface method
>> acquired from findVirtual to an indy call site:
>>
>> #
>> # A fatal error has been detected by the Java Runtime Environment:
>> #
>> #  Internal Error (methodHandleWalk.cpp:1111), pid=24843, tid=2962804736
>> #  Error: Unimplemented()
>> #
>> # JRE version: 7.0
>> # Java VM: OpenJDK Server VM (21.0-b09 mixed mode bsd-x86 )
>> # Failed to write core dump. Core dumps have been disabled. To enable
>> core dumping, try "ulimit -c unlimited" before starting Java again
>> #
>> # An error report file with more information is saved as:
>> # /Users/headius/projects/jruby/hs_err_pid24843.log
>> [thread -1332695040 also had an error]
>> #
>> # If you would like to submit a bug report, please visit:
>> #   http://bugreport.sun.com/bugreport/crash.jsp
>> #
>> Abort trap
>
> It seems nobody (including me) has ever bound an interface before that was hot to be compiled in the compiler.  I need a small test case to add the missing code (which should be trivial).

But like with a bounded invokevirtual, there is no profile information 
available so
using a cascade of GWT (i.e. our own inlining cache) should be more 
efficient here.

> -- Christian

Rémi