supporting tracing.  That should be moved to a "runtime" directory.

llvm-svn: 2660

llvm-svn: 2625

llvm-svn: 2614

llvm-svn: 2613

llvm-svn: 2602

llvm-svn: 2594

Now it only output llvm or C code.

llvm-svn: 2564

llvm-svn: 2557

llvm-svn: 2556

llvm-svn: 2552

llvm-svn: 2551

llvm-svn: 2538

llvm-svn: 2532

llvm-svn: 2531

llvm-svn: 2524

the Scalar and Utils subdirectories

llvm-svn: 2523

llvm-svn: 2520

llvm-svn: 2503

them with an DIE pass before more expensive optimizations are run.

llvm-svn: 2491

llvm-svn: 2476

llvm-svn: 2421

llvm-svn: 2412

Include the SCCP pass in gccas

llvm-svn: 2410

llvm-svn: 2401

llvm-svn: 2397

to make debugging output a lot nicer.

llvm-svn: 2395

llvm-svn: 2388

Tighten up the AnalysisUsage of lots of passes, primarily to correctly indicate whether or not they invalidate the CFGA

llvm-svn: 2386

llvm-svn: 2371

llvm-svn: 2365

linking the final program to allow smarter optimizations

llvm-svn: 2364

llvm-svn: 2360

llvm-svn: 2340

llvm-svn: 2339

llvm-svn: 2336

  - Rename runOnMethod to runOnFunction
* Transform getAnalysisUsageInfo into getAnalysisUsage
  - Method is now const
  - It now takes one AnalysisUsage object to fill in instead of 3 vectors
    to fill in
  - Pass's now specify which other passes they _preserve_ not which ones
    they modify (be conservative!)
  - A pass can specify that it preserves all analyses (because it never
    modifies the underlying program)
* s/Method/Function/g in other random places as well

llvm-svn: 2333

written output file.  This is important because crashing testcases often write
part of a file out, and the testing harness decides the file is up-to-date next
time the test is run.

llvm-svn: 2303

* s/Method/Function/

llvm-svn: 2234

llvm-svn: 2231

  FunctionResolvingPass one.
* We run it *after* the symbol stripping pass so that -strip can be
  pipelined with the constant merging pass or something else if desired.

llvm-svn: 2226