http://llvm.org/bugs/show_bug.cgi?id=7822
Summary: vmkit: lazy compilation fails when triggered from AOT
compiled code
Product: new-bugs
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P
Component: new bugs
AssignedTo: [email protected]
ReportedBy: [email protected]
CC: [email protected]
Using the default J3 lazy compiler, AOT compiled code that calls a stub and
triggers a lazy compilation will crash vmkit. The problem appears to be that
the J3 lazy compiler uses debug information of the caller of the stub to
determine the constant pool entry that corresponds with the stubbed method.
AOT compiled code is missing this debug information, which causes vmkit to
crash.
Test case I've been using is trying to run the dacapo benchmarks
(www.dacapobench.org). Run the following with a precompiled libvmjc.so:
$ CLASSPATH=dacapo-9.12-bach.jar vmkit -java Harness -l
I received a SIGSEGV: either the VM code or an external
native method is bogus. Aborting...
Segmentation fault
$
Using the LLVM lazy compiler works (as does running without libvmjc.so):
$ CLASSPATH=dacapo-9.12-bach.jar vmkit -llvm-lazy -java Harness -l
avrora batik eclipse fop h2 jython luindex lusearch pmd sunflow tomcat
tradebeans tradesoap xalan
$
--
Configure bugmail: http://llvm.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
_______________________________________________
LLVMbugs mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/llvmbugs
