search for: llvm_executionengin

...docs. llvm[1]: Installing HTML documentation llvm[1]: Building ocamldoc documentation llvm[3]: Documenting llvm.odoc llvm[3]: Documenting llvm_bitreader.odoc llvm[3]: Documenting llvm_bitwriter.odoc llvm[3]: Documenting llvm_analysis.odoc llvm[3]: Documenting llvm_target.odoc llvm[3]: Documenting llvm_executionengine.odoc llvm[4]: Documenting llvm_scalar_opts.odoc Fatal error: exception Failure("There are two interfaces of module Llvm_analysis.") make[1]: *** [regen-ocamldoc] Error 2 make: *** [install] Error 1 This error does not happen when I install in Release mode or Debug mode. It only happens...

Hi all, Here's an example of how to LLVM's JIT compiler/interpreter from Ocaml. $ cat jithelloworld.ml (* jithelloworld.ml *) open Llvm open Llvm_executionengine let execute_function f m = (* Set up the JIT. *) let jit = ExecutionEngine.create (ModuleProvider.create m) in ExecutionEngine.run_static_ctors jit; (* Execute the function. *) ignore (ExecutionEngine.run_function f [| |] jit); (* Tear down the JIT. *) ExecutionEngine.run_s...

...rpret or, and evaluating a function, as what http://llvm.org/docs/tutorial/OCamlLangImpl4.html shows. But LLVM has not exposed the LLVM interfaces to design a new JIT like http://llvm.org/docs/WritingAnLLVMBackend.html#jitSupport. I did not find such bindings from bindings/ocaml/executionengine/llvm_executionengine.ml. Please fix me if I am wrong. > > Several major projects are using OCaml's LLVM bindings to execute non-trivial > code via JIT. Could you please point out what these projects are? I am very interested in looking into these projects to see if they exposed any more LLVM interfaces,...

On Wednesday 24 February 2010 03:58:03 Jianzhou Zhao wrote: > I think LLVM OCaml bindings do not support JIT too much. Can you elaborate on this? Several major projects are using OCaml's LLVM bindings to execute non-trivial code via JIT. -- Dr Jon Harrop, Flying Frog Consultancy Ltd. http://www.ffconsultancy.com/?e

...ot; from llvm-config into "-cclib x -cclib y - cclib z", which instructs ocaml to pass "x y z" down to the linker when creating an executable. The UsedComponents variable originates in this case from bindings/ocaml/executionengine/Makefile: LEVEL := ../../.. LIBRARYNAME := llvm_executionengine DONT_BUILD_RELINKED := 1 UsedComponents := executionengine jit interpreter native UsedOcamlInterfaces := llvm llvm_target include ../Makefile.ocaml I don't see anything obviously wrong here; it seems that llvm-config - ldflags executionengine jit interpreter native should be invoked, whic...

...================================================= > --- llvm/trunk/test/Bindings/Ocaml/executionengine.ml (original) > +++ llvm/trunk/test/Bindings/Ocaml/executionengine.ml Wed Oct 22 > 07:41:54 2008 > @@ -1,4 +1,4 @@ > -(* RUN: %ocamlc -warn-error A llvm.cma llvm_target.cma > llvm_executionengine.cma %s -o %t > +(* RUN: %ocamlc -warn-error A llvm.cma llvm_target.cma > llvm_executionengine.cma %s -o %t 2> /dev/null > * RUN: ./%t %t.bc > *) > > > Modified: llvm/trunk/test/Bindings/Ocaml/scalar_opts.ml > URL: http://llvm.org/viewvc/llvm-project/llvm/trunk/test/B...

I have an issue with the OCaml build system and the ExecutionEngine. PR2128 has a patch to change the Interpreter to use libffi. This breaks test/Bindings/Ocaml/executionengine.ml because OCaml doesn't try to link with libffi, even though llvm-config knows that we should: $ Debug/bin/llvm-config --ldflags interpreter -L/home/nicholas/llvm-commit/Debug/lib -lpthread -lffi -ldl -lm

...LVMAnalysis.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-apple-darwin8-g++-4.0.1: /opt/local/var/macports/build/_Users_Shared_erickt_Projects_macports_dports.git_lang_llvm/work/build/Release/lib/LLVMX86.o: No such file or directory i686-apple-darwin8-g++-4.0.1: /opt/local/var/macports/build/_Users_Shared...

I have committed the changes to HLVM that bring it up to date with respect to the new LLVM 2.6 release: http://hlvm.forge.ocamlcore.org/ This required handling of llcontexts and the injection of a call to the new Llvm_executionengine.initialize_native_target function (that is undocumented) *before* the JIT EE is created, otherwise LLVM resorts to the LLVM interpreter which breaks at run-time because it does not fully implement the IR generated by HLVM. I've also replaced the garbage collector with a more conventional i...

...m from outside the build tree (ie move the source into my own subtree), I run into problems. When I try to build (ocamlbuild toy.byte) after moving the llvm_* .cma, .cmo. .cmx .cmxa and .a into the local directory, I get the following error. + /usr/local/bin/ocamlc.opt llvm.cma llvm_analysis.cma llvm_executionengine.cma llvm_target.cma llvm_scalar_opts.cma -cc clang++ ast.cmo token.cmo parser.cmo codegen.cmo lexer.cmo toplevel.cmo toy.cmo bindings.o -o toy.byte clang: warning: treating 'c' input as 'c++' when in C++ mode, this behavior is deprecated ld: library not found for -lllvm_scalar_opts...

...formats nicely with ocamldoc. It does not yet hook into the build system, though. --- bindings/ocaml/analysis/llvm_analysis.mli | 21 +- bindings/ocaml/bitreader/llvm_bitreader.mli | 13 +- bindings/ocaml/bitwriter/llvm_bitwriter.mli | 11 +- .../ocaml/executionengine/llvm_executionengine.mli | 118 ++-- bindings/ocaml/llvm/llvm.ml | 1 - bindings/ocaml/llvm/llvm.mli | 587 ++++++++++---------- 6 files changed, 373 insertions(+), 378 deletions(-) -------------- next part -------------- A non-text attachment was scrubbed... Name: 635...

...mory allocation implementation > that will work with a JIT? > > 3. Do the OCaml LLVM bindings even allow using LLVM in JIT mode? I think LLVM OCaml bindings do not support JIT too much. All the exposed C++ interfaces, which are possibly relative to JIT, are /bindings/ocaml/executionengine/llvm_executionengine.ml. But you could be able to expose more JIT interfaces into OCaml. > > And of course, if anyone has experience writing a JIT using LLVM, or using > the OCaml LLVM bindings, any advice you may have will be greatly > appreciated. > -- > View this message in context: http://old.na...

...a function, > as what http://llvm.org/docs/tutorial/OCamlLangImpl4.html shows. > But LLVM has not exposed the LLVM interfaces to design a new JIT > like http://llvm.org/docs/WritingAnLLVMBackend.html#jitSupport. > I did not find such bindings from > bindings/ocaml/executionengine/llvm_executionengine.ml. > Please fix me if I am wrong. Your statements are correct but, given that you can write a complete compiler in OCaml using LLVM's JIT compilation, I think it is OTT to say that the "OCaml bindings do not support JIT too much". > > Several major projects are using OC...

...*********** TEST 'LLVM :: Bindings/Ocaml/ext_exc.ml' FAILED ******************** Script: -- /usr/bin/ocamlopt -cc \"g++ -Wall -D_FILE_OFFSET_BITS=64 -D_REENTRANT\" -I /home/rleissa/projects/llvm/build_debug/Debug+Asserts+Checks/lib/ocaml -warn-error A llvm.cmxa llvm_bitreader.cmxa llvm_executionengine.cmxa /home/rleissa/projects/llvm/llvm/test/Bindings/Ocaml/ext_exc.ml -o /home/rleissa/projects/llvm/build_debug/test/Bindings/Ocaml/Output/ext_exc.ml.tmp /home/rleissa/projects/llvm/build_debug/test/Bindings/Ocaml/Output/ext_exc.ml.tmp </dev/null -- Exit Code: 134 Command Output (stderr): -- ex...

...caml/ bitwriter.ml -o bitwriter.ml.tmp 2> /dev/null child process exited abnormally FAIL: /home/ang/svn/llvm/test/Bindings/Ocaml/executionengine.ml Failed with exit(2) at line 1 while running: /usr/bin/ocamlc -cc g++ -I /home/ang/build/llvm/Debug/lib/ocaml - warn-error A llvm.cma llvm_target.cma llvm_executionengine.cma /home/ang/svn/llv m/test/Bindings/Ocaml/executionengine.ml -o executionengine.ml.tmp 2> /dev/null child process exited abnormally FAIL: /home/ang/svn/llvm/test/Bindings/Ocaml/scalar_opts.ml Failed with exit(2) at line 1 while running: /usr/bin/ocamlc -cc g++ -I /home/ang/build/llvm/Debug/li...

...LVMExecutionEngine.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-apple-darwin8-g++-4.0.1: > /opt/local/var/macports/build/ > _Users_Shared_erickt_Projects_macports_dports.git_lang_llvm/work/ > build/Release/lib/LLVMX86.o: > No such file or directory > i686-apple-darwin8-g++-4.0.1...

...gainst the c++ libraries, as in this: /opt/local/bin/ocamlopt -cc g++ -pp camlp4of -I /Users/erickt/Projects/llvm/gcc/llvm-build-Release/examples/OCaml-Kaleidoscope/Chapter7/Release+Asserts -I /Users/erickt/Projects/llvm/gcc/llvm-build-Release/Release+Asserts/lib/ocaml llvm.cmxa llvm_analysis.cmxa llvm_executionengine.cmxa llvm_target.cmxa llvm_scalar_opts.cmxa -o /Users/erickt/Projects/llvm/gcc/llvm-build-Release/examples/OCaml-Kaleidoscope/Chapter7/Release+Asserts/OCaml-Kaleidoscope-Ch7 /Users/erickt/Projects/llvm/gcc/llvm-build-Release/examples/OCaml-Kaleidoscope/Chapter7/Release+Asserts/ast.cmx /Users/erick...

Hello, For a course project, I am required to write a compiler for some language of my choice, and this compiler has to be implemented in a functional language. I have chosen create a *JIT* compiler for C source, and to implement my compiler in OCaml using LLVM for the back-end. I have experience using LLVM in C++ (I wrote a MATLAB JIT compiler not long ago), however, I am a bit puzzled as to how

On Mon, Feb 23, 2009 at 12:12 AM, Aaron Gray < aaronngray.lists at googlemail.com> wrote: > On Sun, Feb 22, 2009 at 11:15 PM, Anton Korobeynikov < > anton at korobeynikov.info> wrote: > >> >> Actually its [configure-stage3-intl] where its hanging. >> >> This can easily be due to inline FP math in the stdlib headers. For >> example - I had to