search for: javaruntimejit

...ariables that no longer exist (I assume because they were moved into TargetOptions). I attempted to make some minor fixes to get by this and I did, but when it was building mmtk-vmkit.jar (I think that's what it is doing) I got an assertion while running the vmjc command in the Makefile: vmjc: JavaRuntimeJIT.cpp:469: void *j3ResolveSpecialStub(): Assertion `FI->Metadata != __null && "Wrong stack trace"' failed. So, either my "fixes" were bad, or I have another problem that I don't know how to solve :) Should I be grabbing a specific version of LLVM/Clang from SV...

Hi all, I tried the step of the Getting Started page (http://vmkit.llvm.org/get_started.html) on Linux/x64 but I had no luck. I could build them. But when I tried to execute J3, it shows like follows, >> j3: JavaRuntimeJIT.cpp:367: void* j3StartJNI(uint32*, uint32**, mvm::KnownFrame*): Assertion `th->getLastSP() == th->lastKnownFrame->currentFP' failed. Does anybody know if the latest LLVM works with the latest VMkit? Which version of LLVM should I use? I also tried VMkit with MMtk and I could not let i...

...modification that I needed to make was to add -L/usr/X11R6/lib to LDFLAGS for compiling the GNU classpath library. However, any attempt at running Java code with j3 results in a crash: Assertion failed: (ctpIndex && "No constant pool index"), function j3ResolveSpecialStub, file JavaRuntimeJIT.cpp, line 708. I don't have the slightest idea what I could do about this. Suggestions are welcome! Konrad.

...t; make was to add -L/usr/X11R6/lib to LDFLAGS for compiling the GNU classpath > library. > > However, any attempt at running Java code with j3 results in a crash: > > Assertion failed: (ctpIndex && "No constant pool index"), function > j3ResolveSpecialStub, file JavaRuntimeJIT.cpp, line 708. > > I don't have the slightest idea what I could do about this. Suggestions are > welcome! > > Konrad. > > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >...

Hi Does anybody use *StartJnjvmWithJIT* from jvjvm.cpp in VMKit? Becuase , I am looking to use without JIT when we are running the Java byte code. My concern is StartJnjvmWithJIT getting three argument *int argc, char** argv, char* mainClass* - why we need to pass *argv and mainclass* arguments here? please help me on this. Regards Sri. -------------- next part -------------- An

...HelloWorld.class.s > HelloWorld.class.sed.s) before assembling. I don't > know if this is a reasonable hack or if it's causing problems. > > * I get the following error at runtime (because some fields are NULL) > and I can't make progress: > > HelloWorld.class.exe: JavaRuntimeJIT.cpp:381: void > *j3ResolveVirtualStub(j3::JavaObject *): Assertion `FI->Metadata != __null > && "Wrong stack trace"' failed. > > > > Am I on the right path, or should I be considering other methods? Or > wrong entirely? > > > > Ultimately,...

...39;/_buf$/ s/globl/weak/' HelloWorld.class.s > HelloWorld.class.sed.s) before assembling. I don't know if this is a reasonable hack or if it's causing problems. * I get the following error at runtime (because some fields are NULL) and I can't make progress: HelloWorld.class.exe: JavaRuntimeJIT.cpp:381: void *j3ResolveVirtualStub(j3::JavaObject *): Assertion `FI->Metadata != __null && "Wrong stack trace"' failed. Am I on the right path, or should I be considering other methods? Or wrong entirely? Ultimately, I propose changing `llcj` into something like a Pytho...

Hi, I just did a reconfigure and rebuild with the latest svn for vmkit code. The code still seg faults but the stack trace seems to have changed. llvm[2]: Building Debug+Asserts mmtk-vmkit.jar all vmjc: JavaRuntimeJIT.cpp:172: uint32 j3VirtualTableLookup(j3::Class*, uint32, uint32*, j3::JavaObject*): Assertion `dmeth->classDef->isInitializing() && "Class not ready in a virtual lookup."' failed. 0 vmjc 0x0904fc0a 1 vmjc 0x0904f997 2 0xb77ac400 _...

...mail.com> wrote: > >> Hi, >> I just did a reconfigure and rebuild with the latest svn for vmkit code. >> >> The code still seg faults but the stack trace seems to have changed. >> >> >> llvm[2]: Building Debug+Asserts mmtk-vmkit.jar all >> vmjc: JavaRuntimeJIT.cpp:172: uint32 j3VirtualTableLookup(j3::Class*, >> uint32, uint32*, j3::JavaObject*): Assertion >> `dmeth->classDef->isInitializing() && "Class not ready in a virtual >> lookup."' failed. >> 0 vmjc 0x0904fc0a >> 1 vmjc...

...3 AM, Akshat Gupta <g.akshat at gmail.com> wrote: > Hi, > I just did a reconfigure and rebuild with the latest svn for vmkit code. > > The code still seg faults but the stack trace seems to have changed. > > > llvm[2]: Building Debug+Asserts mmtk-vmkit.jar all > vmjc: JavaRuntimeJIT.cpp:172: uint32 j3VirtualTableLookup(j3::Class*, > uint32, uint32*, j3::JavaObject*): Assertion > `dmeth->classDef->isInitializing() && "Class not ready in a virtual > lookup."' failed. > 0 vmjc 0x0904fc0a > 1 vmjc 0x0904f997 > 2...

...;> Hi, >>> I just did a reconfigure and rebuild with the latest svn for vmkit code. >>> >>> The code still seg faults but the stack trace seems to have changed. >>> >>> >>> llvm[2]: Building Debug+Asserts mmtk-vmkit.jar all >>> vmjc: JavaRuntimeJIT.cpp:172: uint32 j3VirtualTableLookup(j3::Class*, >>> uint32, uint32*, j3::JavaObject*): Assertion >>> `dmeth->classDef->isInitializing() && "Class not ready in a virtual >>> lookup."' failed. >>> 0 vmjc 0x0904fc0a >>&...

I just noticed there was some .h move around in llvm and fixed the includes in vmkit. Maybe you were just removing the failing includes? In any case, I have updated vmkit for llvm trunk. Let me know if updating helps. Nicolas On Fri, Aug 26, 2011 at 12:00 PM, Akshat Gupta <g.akshat at gmail.com> wrote: > Yep, I am compiling with llvm-gcc. Also I removed the LD flag on the >

Yep, I am compiling with llvm-gcc. Also I removed the LD flag on the configure, it still gives the same segafault. Thanks, Akshat On Fri, Aug 26, 2011 at 4:21 AM, Nicolas Geoffray < nicolas.geoffray at gmail.com> wrote: > On Fri, Aug 26, 2011 at 1:08 AM, Akshat Gupta <g.akshat at gmail.com> wrote: > >> Hi, >> >> Here are my build details. >> OS: >>