similar to: [LLVMdev] How to add a pass to JIT

Hi, On LLVM 2.8, on executing following command ../install/bin/lli test.bc It gives following error "UNREACHABLE executed! 0 lli 0x08699718 Stack dump: 0. Program arguments: ../install/bin/lli test.bc 1. Running pass 'X86 Machine Code Emitter' on function '@main' Aborted" But, ../install/bin/llc test.bc :- does not give any error. Also, This problem does not occur

On 5/6/11 3:31 PM, pracheeyogi at cse.iitb.ac.in wrote: > Hi, > > On LLVM 2.8, on executing following command > ../install/bin/lli test.bc > > It gives following error > > "UNREACHABLE executed! > 0 lli 0x08699718 > Stack dump: > 0. Program arguments: ../install/bin/lli test.bc > 1. Running pass 'X86 Machine Code Emitter' on function

Hi all, I can't find a way to add a MachineFunctionPass to the common codegen passes (LLVMTargetMachine::addPassesToEmitMachineCode) while JITting (the pass manager is associated with the jitstate of the JIT and I can't access it because it's private). Have I missed something? Or adding a MachineFunctionPass to codegen requires to change the

First, I'm not sure if deleting the ExecutionEngine is all I need to clean-up... so I started with a minimal test just to check int main( int argc, char **argv ){ while( true ){ Module *M = new Module("M"); Function *F = cast<Function>(M->getOrInsertFunction("F", Type::Int32Ty, (Type*)0)); BasicBlock *BB = new

I am creating an ExecutionEngine using the LLVMCreateExecutionEngineForModule function from the C API. I am get a set fault with the following backtrace. Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_INVALID_ADDRESS at address: 0x0000000000000120 0x0000000107c06643 in llvm::LLVMTargetMachine::addCommonCodeGenPasses () (gdb) bt #0 0x0000000107c06643 in

On 2007-07-14, at 13:56, Anton Korobeynikov wrote: >> You can find out what exactly leaks with the help of valgrind. > > It seems, that Paolo is on Mac OS X. No valgrind there :( All is not lost… http://developer.apple.com/documentation/Performance/Conceptual/ ManagingMemory/Articles/FindingLeaks.html — Gordon

On Sun, 15 Jul 2007, Paolo Invernizzi wrote: > First, I'm not sure if deleting the ExecutionEngine is all I need to > clean-up... so I started with a minimal test just to check Is this llvm 2.0 or llvm svn head? Several minor memory leaks have been fixed since llvm 2.0. -Chris > int main( int argc, char **argv ){ > while( true ){ > Module *M = new

Hello, Please, I need more information on the runtime optimizer used in the LLVM JIT. - Where can I find it in the LLVM source code? - Are those runtime optimizations done on the LLVM representation code or on the machine code? Sara -------------- next part -------------- An HTML attachment was scrubbed... URL:

Holger. > You can find out what exactly leaks with the help of valgrind. It seems, that Paolo is on Mac OS X. No valgrind there :( -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

Hi, I am working on an LLVM backend for GPUs, and I would like to be able to emit a very simple byte stream of machine code, so that it can be fed directly into the GPU. I don't need anything fancy, just the raw machine code, one instruction after another. I think I've already implemented everything in the backend that is required to do this, but I'm not sure how to get a pointer to

Hi, I know using llc i can print machine code (-print-machineinstrs). How can i print machine code using llvm c++ api.. i looked into llc code but not able to find it.. Thanks & Regards, Pachauri

Thanks Evan. On 09/11/2007, at 6:50 PM, Evan Cheng wrote: >> 1. What optimization passes, if any, should I run on the module >> before I pass it to the ExecutionEngine. > > The default JIt driver, lli, runs everything. My reading of the lli source indicates that it's not explicitly doing any opt passes - is that happening implicitly in the ExecutionEngine? I can see

Dear all The following process is about trying to do the " live migration at the same time with 5 Virtual machines ", but there is somthing problem with it. Process: yogi-pc2: # xm migrate --live vm01 pc2 & xm migrate --live vm02 pc2 & xm migrate --live vm03 pc2 & xm migrate --live vm04 pc2 & xm migrate --live vm05 pc2[1] 29983 [2] 29984 [3] 29985 [4]

On Sep 14, 2009, at 10:54 PM, Nicolas Geoffray wrote: > Hi all, > > I can't find a way to add a MachineFunctionPass to the common codegen > passes (LLVMTargetMachine::addPassesToEmitMachineCode) while JITting > (the pass manager is associated with the jitstate of the JIT and I > can't > access it because it's private). Have I missed something? Or adding a >

Hi! I'm looking for a way to make the the "llc" tool (or any other tool), directly produce a binary file for some target. The TargetMachine class has a method 'addPassesToEmitMachineCode', that's suitable for that, but that method also requires an instance of MachineCodeEmitter. The existing MachineCodeEmitter derived classes are either debug-only (writing to

I have done that. I have defined createMyAnaPass() in Passes.h and it is defined in MyAna.cpp and used in LinkAllPasses.h But still the error : /home/ambika/llvm/llvm-obj/tools/opt/Release/opt.o: In function `global constructors keyed to opt.cpp': opt.cpp:(.text+0x1e89): undefined reference to `llvm::createMyAnaPass()' I dont understand whats the problem. Jianzhou Zhao wrote: >

-------------- next part -------------- An embedded message was scrubbed... From: ambika <ambika at cse.iitb.ac.in> Subject: [LLVMdev] Can someone help me with error while i make my own pass Date: Thu, 08 Apr 2010 21:40:25 +0530 Size: 4901 URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100411/33876147/attachment.eml>

Tried that but still no success Chris Lattner wrote: > Try doing a clean build, then doing 'make ENABLE_PIC=1' > > -Chris > > On Apr 11, 2010, at 9:13 AM, ambika wrote: > >> >> >> *From: *ambika <ambika at cse.iitb.ac.in <mailto:ambika at cse.iitb.ac.in>> >> *Date: *April 8, 2010 9:10:25 AM PDT >> *To: *llvmdev at cs.uiuc.edu

Chris Lattner wrote: >> The TargetMachine class has a method 'addPassesToEmitMachineCode', that's >> suitable for that, but that method also requires an instance of >> MachineCodeEmitter. > > Actually, you probably want to plug into the addPassesToEmitFile API, when > FileType is set to ObjectFile. X86TargetMachine::addPassesToEmitFile > demonstrates

Thanks that helped me out. But now I am facing one more problem. It says : ‘llvm::ModulePass* llvm::createMyAnaPass()’ should have been declared inside ‘llvm’ but I can find no place to declare it. Where should I do it. John Criswell wrote: > ambika at cse.iitb.ac.in wrote: >> Hi, >> >> I am trying to add a pass inn LLVM, and I actually want to add it in >> source