llvm-svn: 42575

Patch by Adam Goode.

llvm-svn: 42574

llvm-svn: 42573

llvm-svn: 42570

llvm-svn: 42565

seem significant as well.

llvm-svn: 42564

each one's runOnFunction method.

llvm-svn: 42563

llvm-svn: 42554

llvm-svn: 42552

llvm-svn: 42549

llvm-svn: 42548

llvm-svn: 42547

llvm-svn: 42546

llvm-svn: 42542

llvm-svn: 42541

llvm-svn: 42540

llvm-svn: 42537

llvm-svn: 42533

stdlib if it's beneath --prefix, and is libdir/ocaml otherwise.

If someone has a better way than this to test whether $B is a path
within $A, I'd love to hear it:

  if test "$A" \< "$B" -a "$B" \< "${A}~"

llvm-svn: 42532

llvm-svn: 42529

llvm-svn: 42528

llvm-svn: 42527

llvm-svn: 42526

llvm-svn: 42522

llvm-svn: 42521

llvm-svn: 42519

llvm-svn: 42517

If the user did not check out LLVM and request it to be built, it should be a build error. This relies on the user having a successful build of LLVM, but the tests will fail if they dont. 

llvm-svn: 42514

instructions reverse map.

llvm-svn: 42509

llvm-svn: 42508

SourceFiles list is fully filled in so that it sees all of the files.

llvm-svn: 42506

llvm-svn: 42505

llvm-svn: 42502

llvm-svn: 42499

Relax unsafe use check. If there is one unconditional use inside the loop then it is safe to promote value even if there is another conditional use inside the loop.

llvm-svn: 42493

llvm-svn: 42492

llvm-svn: 42488

llvm-svn: 42487

llvm-svn: 42486

use APFloat for int-to-float/double; use
round-to-nearest for these (implementation-defined,
seems to match gcc).

llvm-svn: 42484