search for: vmkitgcprinter

...g StaticGCPass.ll to StaticGCPass.bc for Release+Asserts build (bytecode) llvm[1]: Building Release+Asserts Bytecode Archive libStaticGCPass.bca make[1]: Leaving directory `.../vmkit/lib/vmkit/StaticGCPass' make[1]: Entering directory `.../vmkit/lib/vmkit/StaticGCPrinter' llvm[1]: Compiling VmkitGCPrinter.cpp for Release+Asserts build (PIC) VmkitGCPrinter.cpp: In member function ‘virtual void {anonymous}::VmkitAOTGCMetadataPrinter::finishAssembly(llvm::AsmPrinter&)’: VmkitGCPrinter.cpp:292:63: error: no matching function for call to ‘llvm::DataLayout::getPointerSize() const’ VmkitGCPrinter.cpp:2...

...ring directory `/home/callum/vmkit/vmkit/lib/vmkit/StaticGCPass' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/home/callum/vmkit/vmkit/lib/vmkit/StaticGCPass' make[1]: Entering directory `/home/callum/vmkit/vmkit/lib/vmkit/StaticGCPrinter' llvm[1]: Compiling VmkitGCPrinter.cpp for Release+Asserts build (PIC) VmkitGCPrinter.cpp: In member function ‘virtual void {anonymous}::VmkitAOTGCMetadataPrinter::finishAssembly(llvm::AsmPrinter&)’: VmkitGCPrinter.cpp:292:63: error: no matching function for call to ‘llvm::DataLayout::getPointerSize() const’ VmkitGCPrinter.cpp...

...hello.bc llc /home/shyam/llvmbuild/Release+Debug+Asserts/bin/llc /tmp/llvm_Wa4yw2/hello.bc -disable-fp-elim -disable-branch-fold -disable-cfi -disable-debug-info-print -load=/home/shyam/classpath-0.97.2/lib/vmkit/Release+Debug+Asserts/lib/StaticGCPrinter.so -o /tmp/llvm_Wa4yw2/hello.s (null) llc: VmkitGCPrinter.cpp:283: llvm::Constant* FindMetadata(const llvm::Function&): Assertion `0 && "Should have found a JavaMethod"' failed.0 llc 0x08c83b58Stack dump:0. Program arguments: /home/shyam/llvmbuild/Release+Debug+Asserts/bin/llc /tmp/llvm_Wa4yw2/hello.bc -disable-fp-elim -disable-...

..."Gaël Thomas" <gael.thomas00 at gmail.com> a écrit : > Hi Brian, > > So, I confirm, llc is not more maintained. And using vmjc is probably > the good starting point to translate Java bytecode into llvm bitcode. > > However, I think that your hack (changing the way VMKitGCPrinter.cpp > resolves symbols) is probably not the good way to solve the initial > problem. And maybe that your current problem is simply a consequence > of the mangling problem. So, let's start with the first problem :) > > So, I answer in your previous mail. As it's the beginning...

...o be target-independent. Any advice is welcome! Thank you in advance, Yiannis [1]: https://groups.google.com/group/llvm-dev/browse_thread/thread/c866ef40b31504cb/46ab6820f20aba38?show_docid=46ab6820f20aba38&pli=1 [2]: http://llvm.org/viewvc/llvm-project/vmkit/trunk/lib/vmkit/StaticGCPrinter/VmkitGCPrinter.cpp?view=markup -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20111123/b70b4d17/attachment.html>

...#39;m tripping an assertion that I don't quite understand yet. I'm just curious if anybody can point me in the right direction. $ javac helloworld.java $ vmjc -o helloworld.bc helloworld.class $ llc -load=<...>/Release+Asserts/lib/StaticGCPrinter.so helloworld.bc -o helloworld.s llc: VmkitGCPrinter.cpp:268: llvm::Constant* FindMetadata(const llvm::Function&): Assertion `0 && "Should have found a JavaMethod"' failed. 0 llc 0x000000000103726f 1 llc 0x0000000001037799 2 libpthread.so.0 0x00007fea25133cb0 3 libc.so.6 0x00007f...

Hello again Gaël, (et al) More on rekindling work on VMKit! Thank you for your interactions thus far on- and off-list. As you suggested in your VMKit-retirement email (to which I'm attempting to respond), I'm interested in producing a Java-to-LLVM compiler out of VMKit. I'd like to take you up on your offer to help understand the architecture. If I can get the a Java-to-LLVM

Greetings, I've been using LLVM and Clang for some time, but I'm new to the list and new to VMKit; please advise if I should post this elsewhere. VMKit doesn't seem to build with LLVM/Clang 3.4.2 -- seems that one must use LLVM3.3. I see the following error: VmkitGCPrinter.cpp:363:53: error: too many arguments to function call, expected 2, have 3 AP.OutStreamer.EmitValue(address, IntPtrSize, 0); I now see the vmkit build instructions (http://vmkit.llvm.org/get_started.html) explicitly say to use LLVM and Clang 3.3; using that version fixes the above. It seems...

Hi, I'm new to VMKit and I'm trying to use its AOT Java compiler but I'm immediately getting an error message which I don't understand. Everything was compiler as suggested in the Getting Started tutorial, using GNU Classpath. I try to run: llcj ../../tools/trainer/Release+Asserts/HelloWorld.class and get the following output: Can not materiale a function in AOT mode.0