- Jan 07, 2013
-
-
Chandler Carruth authored
library rename. llvm-svn: 171747
-
- Jun 22, 2012
-
-
NAKAMURA Takumi authored
llvm-svn: 158942
-
- Mar 30, 2012
-
-
Rafael Espindola authored
needed for correctness, but still doesn't clean up code that now unnecessary checks for reachability. llvm-svn: 153755
-
- Jan 02, 2012
-
-
Chandler Carruth authored
is testing the bitcode reader's functionality, not VMCore's. Add the what is a hope sufficient build system mojo to build and run a new unittest. Also clean up some of the test's naming. The goal for the file should be to unittest the Bitcode Reader, and this is just one particular test among potentially many in the future. Also, reverse my position and relegate the PR# to a comment, but stash the comment on the same line as the test name so it doesn't get lost. This makes the code more self-documenting hopefully w/o losing track of the PR number. llvm-svn: 147431
-
Chandler Carruth authored
build. This didn't show up in the CMake build because the CMake build for the unittests is rather poorly factored. This probably isn't the correct fix. This should be a bitcode reader unittest not a VMCore unittest. I'll move it and clean various parts of the unittest up in a follow-up patch, but I wanted to unbreak the bots. llvm-svn: 147427
-
- Jun 29, 2009
-
-
Torok Edwin authored
Also don't call finalizers for LoopPass if initialization was not called. Add a unittest that tests that these methods are called, in the proper order, and the correct number of times. llvm-svn: 74438
-
- Mar 24, 2009
-
-
Misha Brukman authored
llvm-svn: 67652
-
- 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
-