search for: llvmlinkinjit

...fix that. > Is it possible that the file where you are including "JIT.h" doesn't have any required code in it? I'm including "JIT.h" directly in the main module, which also uses the engine. See the small test case attached. Even if I bypass the dummy object and call LLVMLinkInJIT() directly, it still gets optimized out... ciao, Mario -------------- next part -------------- /* * vim: set tabstop=4 shiftwidth=4 expandtab: */ #define DEBUG_TYPE "ExecutionEngineTest" #include <llvm/ExecutionEngine/Interpreter.h> #include <llvm/ExecutionEngine/JIT.h> #...

...pport MC emission!" when I call EngineBuilder::create(). I assume that I'm just not doing something necessary for initialization, but I'm not sure what it would be--I am calling all of: llvm::InitializeNativeTarget(); llvm::InitializeAllTargetMCs(); LLVMLinkInMCJIT(); LLVMLinkInJIT(); and the module I'm trying to load does have a reasonable target: target triple = "x86_64-apple-darwin11.0.0" I've attached a short test case that has the sequence of calls that I'm making and one of the bitcode files I'm trying to use. I'd be happy for any guida...

...nitializations and is callable from your target language. That's odd, we don't need to do that for ocaml. Have you tried having a function like this defined in your binding? /* Force the LLVM interpreter and JIT to be linked in. */ void llvm_initialize(void) { LLVMLinkInInterpreter(); LLVMLinkInJIT(); } You don't have to call it, it's just there to make sure the execution engine is actually linked with the binding library.

...:JIT::JIT () #3 0x0000000107eaac21 in llvm::JIT::createJIT () #4 0x0000000107e2cbe4 in llvm::EngineBuilder::create () #5 0x0000000107e315b0 in LLVMCreateExecutionEngineForModule () #6 0x00000001002b1444 in ffi_call_unix64 () at darwin64.S:75 #7 0x00007fff5fbfc130 in ?? () (gdb) I have called LLVMLinkInJIT before this. Can anyone help? -Eric

Yeah, this is a problem with the static constructor getting optimized out. Including "JIT.h" is supposed to fix that. Is it possible that the file where you are including "JIT.h" doesn't have any required code in it? -Andy -----Original Message----- From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Mario Schwalbe Sent: Tuesday,

Hi, I'm on Linux and trying to link an application that makes use of LLVM's JIT execution engine statically. Setup: (1) LLVM libs are compiled as static libraries. (2) Called InitializeNativeTarget(). (3) Included llvm/ExecutionEngine/JIT.h. It works if I build and link regularly. However, if I add -static when linking, the execution engine fails to initialize. Does anyone know why?

...er::create().  I assume that I'm just not doing something necessary for initialization, but I'm not sure what it would be--I am calling all of: >> >>      llvm::InitializeNativeTarget(); >>      llvm::InitializeAllTargetMCs(); >>      LLVMLinkInMCJIT(); >>      LLVMLinkInJIT(); >> >> and the module I'm trying to load does have a reasonable target: >> >> target triple = "x86_64-apple-darwin11.0.0" >> >> I've attached a short test case that has the sequence of calls that I'm making and one of the bitcode files I...

...n I call EngineBuilder::create(). I assume that I'm just not doing something necessary for initialization, but I'm not sure what it would be--I am calling all of: > > llvm::InitializeNativeTarget(); > llvm::InitializeAllTargetMCs(); > LLVMLinkInMCJIT(); > LLVMLinkInJIT(); > > and the module I'm trying to load does have a reasonable target: > > target triple = "x86_64-apple-darwin11.0.0" > > I've attached a short test case that has the sequence of calls that I'm making and one of the bitcode files I'm trying to use. I...

...not doing something necessary for initialization, but I'm not sure what it would be--I am calling all of: >>>> >>>> llvm::InitializeNativeTarget(); >>>> llvm::InitializeAllTargetMCs(); >>>> LLVMLinkInMCJIT(); >>>> LLVMLinkInJIT(); >>>> >>>> and the module I'm trying to load does have a reasonable target: >>>> >>>> target triple = "x86_64-apple-darwin11.0.0" >>>> >>>> I've attached a short test case that has the sequence of calls t...

...CTargetDesc.o): In function `PPCInstPrinter': llvm-svn/lib/Target/PowerPC/MCTargetDesc/../InstPrinter/PPCInstPrinter.h:28: undefined reference to `vtable for llvm::PPCInstPrinter' However, I noticed that lli does neither call InitializeAllTargetMCs(), nor does it call LLVMLinkInMCJIT() and LLVMLinkInJIT(). Adapting my code to lli yields the same problem as for lli (unknown object format). Any more ideas? Best, Ralf Matt Pharr wrote: > Following along from lli code, if you add a call to InitializeNativeTargetAsmPrinter() during setup, it gets a bit farther and crashes rather than issuing that...

...that I'm just not doing something necessary for initialization, but I'm not sure what it would be--I am calling all of: >>> >>> llvm::InitializeNativeTarget(); >>> llvm::InitializeAllTargetMCs(); >>> LLVMLinkInMCJIT(); >>> LLVMLinkInJIT(); >>> >>> and the module I'm trying to load does have a reasonable target: >>> >>> target triple = "x86_64-apple-darwin11.0.0" >>> >>> I've attached a short test case that has the sequence of calls that I'm making and one...

...eRef mx; mx = LLVMBuildMul(builder, mParam, xParam, "mx"); LLVMValueRef y; y = LLVMBuildAdd(builder, mx, bParam, "y"); LLVMValueRef retInst; retInst = LLVMBuildRet(builder, y); (void) retInst; LLVMDisposeBuilder(builder); LLVMLinkInJIT(); LLVMLinkInInterpreter(); LLVMInitializeNativeTarget(); LLVMDumpModule(module); /* Now run it! */ LLVMExecutionEngineRef jit = NULL; char *err; // LLVMBool result = LLVMCreateExecutionEngineForModule(&jit, module, &err); LLVMBool result = LLVM...

It seems that a client application needs to call InitializeNativeTarget or LLVMInitializeNativeTarget before doing any JITting. Unfortunately, LLVMInitializeNativeTarget is defined static inline and does not appear in the .a files; thus a client not written in C or C++ trying to JIT cannot link to the library and call LLVMInitializeNativeTarget that way. It can call a target-specific library

Kenneth Uildriks wrote: > It seems that a client application needs to call > InitializeNativeTarget or LLVMInitializeNativeTarget before doing any > JITting. Unfortunately, LLVMInitializeNativeTarget is defined static > inline and does not appear in the .a files; thus a client not written > in C or C++ trying to JIT cannot link to the library and call >

On Aug 12, 2010, at 10:43 AM, F van der Meeren wrote: > Where am I going wrong here? > Did you link against the library that contains the function? -eric

...------ cmake succeeds in generating the makefile - so it is correctly finding the installed LLVM (2.8, r122491), which compiled fine. The build fails, complaining of: CMakeFiles/nvm.dir/main.cpp.o: In function `global constructors keyed to main': main.cpp:(.text+0x41): undefined reference to `LLVMLinkInJIT' CMakeFiles/nvm.dir/main.cpp.o: In function `main': main.cpp:(.text+0x55): undefined reference to `LLVMInitializeX86TargetInfo' main.cpp:(.text+0x5a): undefined reference to `LLVMInitializeX86Target' ... When I try "jit" in place of "engine" in llvm_config, it c...

...LLVMValueRef mx; mx = LLVMBuildMul(builder, mParam, xParam, "mx"); LLVMValueRef y; y = LLVMBuildAdd(builder, mx, bParam, "y"); LLVMValueRef retInst; retInst = LLVMBuildRet(builder, y); (void) retInst; LLVMDisposeBuilder(builder); LLVMLinkInJIT(); LLVMLinkInInterpreter(); LLVMInitializeNativeTarget(); LLVMDumpModule(module); /* Now run it! */ LLVMExecutionEngineRef jit = NULL; char *err; // LLVMBool result = LLVMCreateExecutionEngineForModule(&jit, module, &err); LLVMBool result = LLVMCreateJIT...

Hello, I'm using the llvm-c bindings for C, but I'm getting some problems, the LLVMCreateExecutionEngine is returning 1 but the error message is an empty string (it's !=NULL). The steps I'm doing is to create the module, then I call LLVMVerifyModule to verify and it works fine, later I call LLVMCreateModuleProviderForExistingModule and it returns !=NULL MP, so it's ok, but

Hello, I have a question concerning llvm-c. I have set up a function that needs to invoke an external method, in a other library. It has the following signature: void* NSFullUserName(void); The void* can be replaced with a i8*, that far I was able to get, but when my call is invoked, the engine gives me the following message: LLVM ERROR: Tried to execute an unknown external function: i8* ()*

...fix that. > Is it possible that the file where you are including "JIT.h" doesn't have any required code in it? I'm including "JIT.h" directly in the main module, which also uses the engine. See the small test case attached. Even if I bypass the dummy object and call LLVMLinkInJIT() directly, it still gets optimized out... ciao, Mario