summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Bytecode/Makefile
Commit message (Collapse)AuthorAgeFilesLines
* lib/Bytecode is deadChris Lattner2007-05-061-14/+0
| | | | llvm-svn: 36889
* don't build bcreader/bcwriterChris Lattner2007-05-061-1/+1
| | | | llvm-svn: 36869
* Add the Archive libraryReid Spencer2004-11-141-1/+1
| | | | llvm-svn: 17764
* There is no reason not to build these in parallelChris Lattner2004-10-151-1/+2
| | | | llvm-svn: 17023
* Remove newly defunct Analyzer directory.Reid Spencer2004-06-291-1/+1
| | | | llvm-svn: 14490
* Commit For New Tool: llvm-abcd (Analysis of ByteCode Dumper). This toolReid Spencer2004-06-071-1/+1
| | | | | | | | | | | | | | | | | | | | | 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
* Added LLVM copyright notice to Makefiles.John Criswell2003-10-201-0/+8
| | | | llvm-svn: 9312
* Initial revisionChris Lattner2001-06-061-0/+5
llvm-svn: 2
OpenPOWER on IntegriCloud