search for: llvmjit

...ing and linking your test case? > How it bombs? > > Do you #include "llvm/ExecutionEngine/JIT.h" ? Hi Oscar, I'm using llvm CVS, and manage to compile/link OK. Yes I include JIT.h. The program segfaults when it gets to calling the function pointer. >From the Makefile: llvmjit: llvmjit.o g++ llvmjit.o /home//users//simonb//lib/LLVMAsmParser.o /home//users//simonb//lib/LLVMInterpreter.o `llvm-config --ldflags` `llvm-config --libs jit` -lpthread -ldl -o llvmjit llvmjit.o: llvmjit.cpp g++ `llvm-config --cxxflags` -c llvmjit.cpp Complete source (i added a call to veri...

Simon Burton <simon at arrowtheory.com> writes: > I'm trying to take assembly and create machine code I can execute. > How close am I ? Your test case is not complete. Besides, which version of llvm are you using? What are the commands for compiling and linking your test case? How it bombs? Do you #include "llvm/ExecutionEngine/JIT.h" ? -- Oscar

Simon Burton <simon at arrowtheory.com> writes: > I'm using llvm CVS, and manage to compile/link OK. Yes I include JIT.h. > The program segfaults when it gets to calling the function pointer. > >>From the Makefile: > > llvmjit: llvmjit.o > g++ llvmjit.o /home//users//simonb//lib/LLVMAsmParser.o /home//users//simonb//lib/LLVMInterpreter.o `llvm-config --ldflags` `llvm-config --libs jit` -lpthread -ldl -o llvmjit > > llvmjit.o: llvmjit.cpp > g++ `llvm-config --cxxflags` -c llvmjit.cpp > > > Complet...

...gt; implementation > > int %globalmul4(int %a) { > % v0 = load int* %my_global_data > % v1 = mul int %v0, 4 > % v2 = add int %v1, %a > store int %v2, int* %my_global_int > ret int %v2 > }''' > > def test_modify_global_data(): > llvmjit.restart() > llvmjit.set_global_data(10) > assert llvmjit.get_global_data() == 10 > gp_data = llvmjit.get_pointer_to_global_data() > llvmjit.add_global_mapping('my_global_data', gp_data) #note: > should be prior to compile() > llvmjit.compile(llglo...

On Wed, 12 Apr 2006 23:02:12 -0500 (CDT) Chris Lattner <sabre at nondot.org> wrote: > > > I'd like to directly create executable code that i can > > stick in memory somewhere and jump into (call). > > Take a look at the llvm/examples directory. There are several small > programs that create LLVM IR on the fly and JIT compile it. I'm trying to take

...gresql12-pltcl postgresql12-plperl-debuginfo.x86_64 : Debug information for package postgresql12-plperl postgresql12-server-debuginfo.x86_64 : Debug information for package postgresql12-server postgresql12-contrib-debuginfo.x86_64 : Debug information for package postgresql12-contrib postgresql12-llvmjit-debuginfo.x86_64 : Debug information for package postgresql12-llvmjit postgresql12-plpython-debuginfo.x86_64 : Debug information for package postgresql12-plpython postgresql12-plpython3-debuginfo.x86_64 : Debug information for package postgresql12-plpython3 ======================================...

...m::orc::ThreadSafeModule, llvm::IntrusiveRefCntPtr<llvm::orc::ResourceTracker>) (LLJIT.cpp:990) | | | ->03.52% (97,354B) 0x840C95B: LLVMOrcLLJITAddLLVMIRModule (OrcV2CBindings.cpp:263) | | | | ->03.52% (97,354B) 0x80639E9: llvm_compile_module (llvmjit.c:608) | | | | ->03.52% (97,354B) 0x8063000: llvm_get_function (llvmjit.c:275) | | | | ->03.52% (97,354B) 0x80758E1: ExecRunCompiledExpr (llvmjit_expr.c:2410) 52 148,049,498,480 3,039,472 2,901,891 137,581 0 ....

...ostgresql12-pltcl postgresql12-plperl-debuginfo.x86_64 : Debug information for package postgresql12-plperl postgresql12-server-debuginfo.x86_64 : Debug information for package postgresql12-server postgresql12-contrib-debuginfo.x86_64 : Debug information for package postgresql12-contrib postgresql12-llvmjit-debuginfo.x86_64 : Debug information for package postgresql12-llvmjit postgresql12-plpython-debuginfo.x86_64 : Debug information for package postgresql12-plpython postgresql12-plpython3-debuginfo.x86_64 : Debug information for package postgresql12-plpython3 ========================================...

...signed long) (/lib/x86_64-linux-gnu/liblsan.so.0+0xf670) #1 0x7fe1bfc1cbc0 in LLVMOrcCreateNewThreadSafeModule (/home/andres/build/llvm-project/master/debug/install/lib/libLLVMOrcJIT.so.12git+0x38bbc0) #2 0x7fe245f6ea6d in llvm_compile_module /home/andres/src/postgresql/src/backend/jit/llvm/llvmjit.c:606 #3 0x7fe245f6e0b0 in llvm_get_function /home/andres/src/postgresql/src/backend/jit/llvm/llvmjit.c:275 #4 0x7fe245f809f1 in ExecRunCompiledExpr /home/andres/src/postgresql/src/backend/jit/llvm/llvmjit_expr.c:2410 #5 0x5633fbb6c17f in ExecEvalExpr /home/andres/src/postgresql/src/inc...

...the same way the Fibonacci >> example does? (See examples/Fibonacci/fibonacci.cpp line 112). > > That works OK. This indicates that the JIT is not working and your code is being interpreted. I don't know about "llvm-config --libs jit" you are using but I would try adding LLVMJIT.o to your link command the same way you do with LLVMInterpreter.o Oh, and renaming your llvmjit.cpp to something else, just in case. (Is the linker case-sensitive?) -- Oscar

On Fri, 14 Apr 2006 03:25:39 +0200 Oscar Fuentes <oscarfv at telefonica.net> wrote: ... > Simon, > > With a fresh CVS checkout, I've tried your test case on Windows/VC++ > and it works ok. Too bad that I have not access to a Linux machine > right now. I'll like to see what's wrong with your test case. > > What you get from running the test case under gdb

...ine /opt/local/lib /opt/local/lib/LLVMX86.o /opt/local/lib/libLLVMSelectionDAG.a /opt/local/lib/libLLVMCodeGen.a /opt/local/lib/libLLVMScalarOpts.a /opt/local/lib/libLLVMTransformUtils.a /opt/local/lib/libLLVMipa.a /opt/local/lib/libLLVMAnalysis.a /opt/local/lib/LLVMExecutionEngine.o /opt/local/lib/LLVMJIT.o /opt/local/lib/libLLVMTarget.a /opt/local/lib/libLLVMCore.a /opt/local/lib/libLLVMSupport.a /opt/local/lib/libLLVMSystem.a > ocamlc -g -cc g++ -I `llvm-config --libdir --libfiles engine` -o toy llvm.cma llvm_analysis.cma llvm_executionengine.cma lexer.cmo parser.cmo codegen.cmo main.ml i686-ap...

...eated. /usr/bin/ld: error in /home/aph/llvm/Release/lib/LLVMInterpreter.o(.eh_frame); n o .eh_frame_hdr table will be created. /usr/bin/ld: error in /home/aph/llvm/Release/lib/LLVMExecutionEngine.o(.eh_frame ); no .eh_frame_hdr table will be created. /usr/bin/ld: error in /home/aph/llvm/Release/lib/LLVMJIT.o(.eh_frame); no .eh_fr ame_hdr table will be created. Configured with: ./configure \ --disable-static \ --enable-assertions \ --enable-debug-runtime \ --enable-jit \ --enable-optimized \ --enable-shared \ --enable-targets=host-only \ --with-pic \ --enable-pic \ --disable-binding Host is x86_64-...

...ng from the cmake >> created VS.NET build. While everything built just fine, the >> ExecutionEngine::create call always returned NULL. The fix was to also >> link with JIT.obj (thanks aKor for pointing me in the right direction). >> I would have thought that linking with LLVMJIT.lib should suffice... a >> VC++ linker issue? >> > > Try adding this to the link command of your executable: > > /INCLUDE:_X86TargetMachineModule > > I should document this somehow. > Yeah, this is necessary, but not sufficient. I also had to link with E...

...usiveRefCntPtr<llvm::orc::ResourceTracker>) (LLJIT.cpp:990) >> | | | ->03.52% (97,354B) 0x840C95B: >> LLVMOrcLLJITAddLLVMIRModule (OrcV2CBindings.cpp:263) >> | | | | ->03.52% (97,354B) 0x80639E9: >> llvm_compile_module (llvmjit.c:608) >> | | | | ->03.52% (97,354B) 0x8063000: >> llvm_get_function (llvmjit.c:275) >> | | | | ->03.52% (97,354B) 0x80758E1: >> ExecRunCompiledExpr (llvmjit_expr.c:2410) >> >> >> 52 148,049,498,480...

...oretically get working .cma's by somehow building the bindings against an installed llvm-config. LLVMers, what's the advantage to building .o files instead of .a's for these libs? LLVMARM.o LLVMAlpha.o LLVMCBackend.o LLVMCellSPU.o LLVMExecutionEngine.o LLVMIA64.o LLVMInterpreter.o LLVMJIT.o LLVMMSIL.o LLVMMips.o LLVMPowerPC.o LLVMSparc.o LLVMX86.o This wouldn't be a problem if these components used .a's instead, since ld's search paths are set up correctly. The options I see are: Use archive libraries instead of objects for the above. Link the above .o files into .a...

...VMInstCombine, "lib\Transforms\InstCombine\LLVMInstCombine.vcproj" LLVMInstrumentation, "lib\Transforms\Instrumentation\LLVMInstrumentation.vcproj" LLVMInterpreter, "lib\ExecutionEngine\Interpreter\LLVMInterpreter.vcproj" LLVMJIT, "lib\ExecutionEngine\JIT\LLVMJIT.vcproj" LLVMLinker, "lib\Linker\LLVMLinker.vcproj" LLVMMC, "lib\MC\LLVMMC.vcproj" LLVMMCParser, "lib\MC\MCParser\LLVMMCParser.vcproj" LLVMScalarOpts, "lib\T...

...compiler with the lib files resulting from the cmake created VS.NET build. While everything built just fine, the ExecutionEngine::create call always returned NULL. The fix was to also link with JIT.obj (thanks aKor for pointing me in the right direction). I would have thought that linking with LLVMJIT.lib should suffice... a VC++ linker issue? 2. There seems to be an issue in ScheduleDAGSDNodes.h when in debug mode. The problem is the evaluation of "&SUnits[0];" which ASSERT's in VC++'s vector[] implementation (when _HAS_ITERATOR_DEBUGGING is on). As a work-around, I c...

...e of these sets, you may need to pull in the rest: LLVMCodeGen.o LLVMSelectionDAG.o libLLVMAnalysis.a libLLVMTarget.a libLLVMTransformUtils.a libLLVMipa.a LLVMSparcV9.o LLVMSparcV9InstrSched.o LLVMSparcV9ModuloSched.o LLVMSparcV9RegAlloc.o LLVMExecutionEngine.o LLVMInterpreter.o LLVMJIT.o The first set is the most problematic: It includes four *.a files, which means that certain linkers will tend to get confused unless you repeat '-l' flags. The odd entry here is libLLVMipa.a, which gets pulled in by something in libLLVMTransformUtils.a, but which doesn't often...

...error in /home/aph/llvm/Release/lib/LLVMInterpreter.o(.eh_frame); n > o .eh_frame_hdr table will be created. > /usr/bin/ld: error in /home/aph/llvm/Release/lib/LLVMExecutionEngine.o(.eh_frame > ); no .eh_frame_hdr table will be created. > /usr/bin/ld: error in /home/aph/llvm/Release/lib/LLVMJIT.o(.eh_frame); no .eh_fr > ame_hdr table will be created. this looks like a bug in gcc: it has created an invalid exception handling frame. I've seen this before, but not while compiling LLVM. > Configured with: > > ./configure \ > --disable-static \ > --enable-assertions \...