for an "i" constraint should get lowered; PR 6309.  While
this argument was passed around a lot, this is the only
place it was used, so it goes away from a lot of other
places.

llvm-svn: 106893

llvm-svn: 106825

llvm-svn: 106824

use ArgOperand API; tighten type of handleFreeWithNonTrivialDependency to be able to use isFreeCall whithout a cast or new overload

llvm-svn: 106823

llvm-svn: 106768

llvm-svn: 106764

enough special case, and it theoretically allows more folding because
it works even when x is unanalyzable.

llvm-svn: 106763

llvm-svn: 106759

llvm-svn: 106752

llvm-svn: 106750

llvm-svn: 106747

llvm-svn: 106745

llvm-svn: 106744

llvm-svn: 106743

llvm-svn: 106740

llvm-svn: 106737

llvm-svn: 106736

llvm-svn: 106734

llvm-svn: 106731

llvm-svn: 106730

llvm-svn: 106729

llvm-svn: 106728

llvm-svn: 106709

llvm-svn: 106707

The ValueMapper used by various cloning utility maps MDNodes also.

llvm-svn: 106706

llvm-svn: 106699

Do not use "ValueMap" as a name for a local variable or an argument.

llvm-svn: 106698

llvm-svn: 106598

is another max which folds. This fixes PR7454.

llvm-svn: 106594

If a metadata operand is seeded in value map and the metadata should also be seeded in value map. This is not limited to function local metadata. 

Failure to seed metdata in such cases causes troubles when in a cloned module, metadata from a new module refers to values in old module. Usually this results in mysterious bugpoint crashes. For example,

 Checking to see if we can delete global inits: Unknown constant!
 UNREACHABLE executed at /d/g/llvm/lib/Bitcode/Writer/BitcodeWriter.cpp:904!

llvm-svn: 106592

llvm-svn: 106591

Reapply Bob's patch.

llvm-svn: 106560

llvm-svn: 106542

llvm-svn: 106529

llvm-svn: 106528

--- Reverse-merging r106508 into '.':
U    lib/Transforms/Utils/CloneModule.cpp

llvm-svn: 106521

llvm-svn: 106508

SmallVector, and other SmallVector simplifications.

llvm-svn: 106452

llvm-svn: 106397

use sharing map. The reconcileNewOffset logic already forces a
separate use if the kinds differ, so incorporating the kind in the
key means we can track more sharing opportunities.

More sharing means fewer total uses to track, which means smaller
problem sizes, which means the conservative throttles don't kick
in as often.

llvm-svn: 106396