aboutsummaryrefslogtreecommitdiff
path: root/bindings/README.txt
diff options
context:
space:
mode:
authorGordon Henriksen <gordonhenriksen@mac.com>2007-09-18 12:49:39 +0000
committerGordon Henriksen <gordonhenriksen@mac.com>2007-09-18 12:49:39 +0000
commit8ef426baa36639458f6777309db25c1768dc9c8a (patch)
tree45ef09f427e18bbf1afd9fd552a3d9fbf0f9e398 /bindings/README.txt
parent54c7e1216415172ac1a2aaafa32668c97f845a2c (diff)
Adding ocaml language bindings for the vmcore and bitwriter libraries. These are
built atop the C language bindings, and user programs can link with them as such: # Bytecode ocamlc -cc g++ llvm.cma llvmbitwriter.cma -o example example.ml # Native ocamlopt -cc g++ llvm.cmxa llvmbitwriter.cmxa -o example.opt example.ml The vmcore.ml test exercises most/all of the APIs thus far bound. Unfortunately, they're not yet numerous enough to write hello world. But: $ cat example.ml (* example.ml *) open Llvm open Llvm_bitwriter let _ = let filename = Sys.argv.(1) in let m = create_module filename in let v = make_int_constant i32_type 42 false in let g = define_global "hello_world" v m in if not (write_bitcode_file m filename) then exit 1; dispose_module m; $ ocamlc -cc g++ llvm.cma llvm_bitwriter.cma -o example example.ml File "example.ml", line 11, characters 6-7: Warning Y: unused variable g. $ ./example example.bc $ llvm-dis < example.bc ; ModuleID = '<stdin>' @hello_world = global i32 42 ; <i32*> [#uses=0] The ocaml test cases provide effective tests for the C interfaces. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@42093 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'bindings/README.txt')
-rw-r--r--bindings/README.txt3
1 files changed, 3 insertions, 0 deletions
diff --git a/bindings/README.txt b/bindings/README.txt
new file mode 100644
index 0000000000..7693cb2cea
--- /dev/null
+++ b/bindings/README.txt
@@ -0,0 +1,3 @@
+This directory contains bindings for the LLVM compiler infrastructure to allow
+programs written in languages other than C or C++ to take advantage of the LLVM
+infrastructure--for instance, a self-hosted compiler front-end.