- Mar 29, 2012
-
-
Danil Malyshev authored
llvm-svn: 153672
-
- Mar 15, 2012
-
-
Eli Bendersky authored
llvm-svn: 152780
-
- Dec 23, 2009
-
-
Jeffrey Yasskin authored
they're available_externally broke VMKit, which was relying on the fact that functions would only be materialized when they were first called. We'll have to wait for http://llvm.org/PR5737 to really fix this. I also added a test for one of the F->isDeclaration() calls which wasn't covered by anything else in the test suite. llvm-svn: 91943
-
- Dec 13, 2009
-
-
Jeffrey Yasskin authored
nlewycky's fix to add -rdynamic so the JIT can look symbols up in Linux builds of the JITTests binary. llvm-svn: 91250
-
- Oct 24, 2009
-
-
http://llvm.org/PR4822Jeffrey Yasskin authored
compiled. When functions are compiled, they accumulate references in the JITResolver's stub maps. This patch removes those references when the functions are destroyed. It's illegal to destroy a Function when any thread may still try to call its machine code. This patch also updates r83987 to use ValueMap instead of explicit CallbackVHs and fixes a couple "do stuff inside assert()" bugs from r84522. llvm-svn: 84975
-
- Jun 25, 2009
-
-
Jeffrey Yasskin authored
emitted or the machine code for a function is freed. Chris mentioned that we may also want a notification when a stub is emitted, but that'll be a future change. I intend to use this to tell oprofile where functions are emitted and what lines correspond to what addresses. llvm-svn: 74157
-
- Jan 01, 2009
-
-
Misha Brukman authored
* Added the first LLVM unittest -- DenseMap. * Updated mkpatch utility to include llvm/unittests dir * Added top-level target "unittests" to run all unittests llvm-svn: 61541
-
- Dec 29, 2007
-
-
Chris Lattner authored
llvm-svn: 45416
-
- Oct 02, 2007
-
-
Gordon Henriksen authored
llvm-svn: 42526
-
- Sep 18, 2007
-
-
Gordon Henriksen authored
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. llvm-svn: 42093
-
- Oct 24, 2005
-
-
Chris Lattner authored
llvm-svn: 23940
-
- Nov 14, 2004
-
-
Reid Spencer authored
llvm-svn: 17773
-
- Nov 12, 2004
-
-
Reid Spencer authored
llvm-svn: 17695
-
- Oct 28, 2004
-
-
Reid Spencer authored
llvm-svn: 17286
-
- Aug 29, 2004
-
-
Reid Spencer authored
independence of the tool. llvm-svn: 16092
-
- Jul 02, 2004
-
-
Reid Spencer authored
llvm-svn: 14555
-
- Jun 30, 2004
-
-
Reid Spencer authored
is no more. llvm-svn: 14498
-
- Jun 07, 2004
-
-
Reid Spencer authored
will (eventually) provide statistical analysis of bytecode files as well as the ability to dump them in a low level format (slot numbers not resolved). The purpose of this is to aid in the Type!=Value change of bug 122. With this initial release, llvm-abcd merely dumps out the bytecode. However, the infrastructure for separating bytecode parsing from handling the parsing events is in place. The style chosen is similar to SAX XML parsing where a handler object is called to handlign the parsing events. This probably isn't useful to anyone but me right now as there is no analysis yet, and the dumper doesn't work on every bytecode file. It will probably be useful by the end of this week. Note that there is some duplication of code from the bytecode reader. This was done to eliminate errors from being introduced in the reader and to minimize the impact to other LLVM developers. At some point, the Analyzer and the Reader will be integrated to use the same infrastructure. Also, sorry for the minor change to Instruction.h but I just couldn't bring myself to write code that depends on Instruction internals. llvm-svn: 14048
-