llvm-svn: 99171

we can reapply the InvokeInst operand reordering patch. (see r98957).

llvm-svn: 99170

so that the SCEVExpander doesn't retain a dangling pointer as its
insert position. The dangling pointer in this case wasn't ever used
to insert new instructions, but it was causing trouble with
SCEVExpander's code for automatically advancing its insert position
past debug intrinsics.

This fixes use-after-free errors that valgrind noticed in
test/Transforms/IndVarSimplify/2007-06-06-DeleteDanglesPtr.ll and
test/Transforms/IndVarSimplify/exit_value_tests.ll.

llvm-svn: 99036

back out r98957, it broke http://smooshlab.apple.com:8010/builders/clang-x86_64-darwin10-fnt/builds/703 in the nightly test suite

llvm-svn: 98958

This time I did a self-hosted bootstrap on Linux x86-64,
with no problems. Let's see how darwin 64-bit self-hosting
goes. At the first sign of failure I'll back this out.

Maybe the valgrind bots give me a hint of what may be wrong
(it at all).

llvm-svn: 98957

str[r]chr returns its pointer argument so we cannot mark it as nocapture. Thanks to Duncan for spotting my mistake.

llvm-svn: 98671

llvm-svn: 98663

llvm-svn: 98584

In "empty" bb, the return instruction may not be first instruction, if dbg value intrinsics are present in this bb. Use terminator to find return instructions. 

llvm-svn: 98565

llvm-svn: 98491

to unify the almost identical code in CodeGenPrepare and InstCombineCalls.

llvm-svn: 98338

llvm-svn: 98297

llvm-svn: 98296

stpcpy is so similar to strcpy, it doesn't deserve a complete copy of the __strcpy_chk -> strcpy code.

llvm-svn: 98284

llvm-svn: 98274

that in InstCombineCalls.

More call lowering needed.

llvm-svn: 98228

compute a set of reachable blocks for itself each time it is called, which
is fairly frequently.

llvm-svn: 98179

out the remainder of the calls that we should lower in some way and
move the tests to the new correct directory. Fix up tests that are now
optimized more than they were before by -instcombine.

llvm-svn: 97875

can be used in more places.  Add an argument for the TargetData that
most of them need. Update for the getInt8PtrTy() change.  Should be
no functionality change.

llvm-svn: 97844

Safely turn memset_chk etc. to non-chk variant if the known object size is >= memset / memcpy / memmove size.

llvm-svn: 97828

in a very specific use pattern embodied in the carefully
reduced testcase.

llvm-svn: 97794

No functionality change.

llvm-svn: 97793

of loops.

llvm-svn: 97642

emitted after the increment. Make sure the insert position
reflects this. This fixes PR6453.

llvm-svn: 97537

a loop and is itself the only dependency).

llvm-svn: 97526

predecessors before returning.  Otherwise, if multiple predecessor edges need
splitting, we only get one of them per iteration.  This makes a small but
measurable compile time improvement with -enable-full-load-pre.

llvm-svn: 97521

llvm-svn: 97512

llvm-svn: 97453

llvm-svn: 97366

llvm-svn: 97313

of a subtle interation in a loop operating in densemap order.

llvm-svn: 97288

argument of createGVNPass and set it automatically for -O3.

llvm-svn: 97245

llvm-svn: 97235

which branch on undef to branch on a boolean constant for the edge
exiting the loop. This helps ScalarEvolution compute trip counts for
loops.

Teach ScalarEvolution to recognize single-value PHIs, when safe, and
ForgetSymbolicName to forget such single-value PHI nodes as apprpriate
in ForgetSymbolicName.

llvm-svn: 97126

llvm-svn: 97036

the DominatorTree. ...", in hopes of restoring poor old PPC bootstrap.

llvm-svn: 97027

argument is non-null, pass it along to PHITranslateSubExpr so that it can
prefer using existing values that dominate the PredBB, instead of just
blindly picking the first equivalent value that it finds on a uselist.
Also when the DominatorTree is specified, have PHITranslateValue filter
out any result that does not dominate the PredBB.  This is basically just
refactoring the check that used to be in GetAvailablePHITranslatedSubExpr
and also in GVN.

Despite my initial expectations, this change does not affect the results
of GVN for any testcases that I could find, but it should help compile time.
Before this change, if PHITranslateSubExpr picked a value that does not
dominate, PHITranslateWithInsertion would then insert a new value, which GVN
would later determine to be redundant and would replace.  By picking a good
value to begin with, we save GVN the extra work of inserting and then
replacing a new value.

llvm-svn: 97010

I don't have a small testcase for this.

llvm-svn: 96890

failures from ValueTable::verifyRemoved() when using -debug.

llvm-svn: 96805

llvm-svn: 96780