llvm-svn: 30154

triplet ordering (large, small, small) explicit with one triplet per line.

llvm-svn: 29839

llvm-svn: 29838

memory pressure. This order spaces out large executables with small ones in
between so that in a -j2 or -j3 build, it only attempts to build only one
large executable at time. If you're doing -j4, you probably have enuogh
memory anyway.

llvm-svn: 29835

Shrinkify LLVM's footprint by removing the analyze tool and moving its
functionality into the opt tool. THis eliminates one of the largest tools
from LLVM and doesn't make opt much bigger because it already included
most of the analysis passes.  To get the old analyze functionality pass
the -analyze option to opt. Note that the integeration here is dead
simple. The "main" of analyze was just copied to opt and invoked if the
-analyze option was given. There may be opportunities for further
integration such as removing the distinction between transform passes
and analysis passes.

To use the analysis functionality, if you previously did this:
  analyze $FNAME -domset -disable-verify
you would now do this:
  opt -analyze $FNAME -domset -disable-verify
Pretty simple.

llvm-svn: 29762

llvm-svn: 29299

llvm-svn: 29289

optional.

llvm-svn: 28570

they can be compiled with ming32. The use of fork(2) has been removed.

llvm-svn: 28369

llvm-svn: 27916

llvm-svn: 27914

llvm-svn: 27913

llvm-svn: 21501

llvm-svn: 19592

correctly omit them for non-Unix operating systems.

llvm-svn: 19206

built on this platform.

llvm-svn: 19015

llvm-db and bugpoint for Win32 rather than add them in
subtr

llvm-svn: 19014

llvm-svn: 19009

that platform without a lot of work because they depend on process image
copy behavior of fork(2).

llvm-svn: 19008

llee was a nice hack, but it wasn't portable so its gone, with Misha's
approval.  Operating systems have facilities available for making bytecode
directly executable without this utility.

llvm-svn: 18916

llvm-svn: 17785

llvm-svn: 17293

llvm-svn: 17233

llvm-svn: 16304

llvm-svn: 16090

llvm-svn: 14568

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

llvm-svn: 13938

llvm-svn: 10688

llvm-svn: 9552

llvm-svn: 9314

llvm-svn: 9161

llvm-svn: 8556

llvm-svn: 8529

llvm-svn: 8506

llvm-svn: 8192

llvm-svn: 6218

llvm-svn: 5135

llvm-svn: 4938

llvm-svn: 4790