llvm-svn: 23991

llvm-svn: 23990

llvm-svn: 23989

llvm-svn: 23988

llvm-svn: 23987

llvm-svn: 23986

llvm-svn: 23985

llvm-svn: 23984

llvm-svn: 23983

llvm-svn: 23982

if the dag combiner isn't run

llvm-svn: 23981

llvm-svn: 23980

llvm-svn: 23979

Remove Function::aiterator and Module::giterator typedefs (and const versions)
as they should have been removed when abegin/gbegin were removed.  Thanks to
alkis for bringing this to my attn.

llvm-svn: 23978

llvm-svn: 23977

llvm-svn: 23976

llvm-svn: 23975

CPU.

llvm-svn: 23974

llvm-svn: 23973

llvm-svn: 23972

llvm-svn: 23971

llvm-svn: 23970

a new project.
Kudos to Rob for suggesting that I add this important step.

llvm-svn: 23969

llvm-svn: 23968

llvm-svn: 23967

llvm-svn: 23966

llvm-svn: 23965

llvm-svn: 23964

for pointing this out!

llvm-svn: 23963

llvm-svn: 23962

one use (but one is a cast).  This handles the very common case of:

 X = alloc [n x byte]
 Y = cast X to somethingbetter
 seteq X, null

In order to avoid infinite looping when there are multiple casts, we only
allow this if the xform is strictly increasing the alignment of the
allocation.

llvm-svn: 23961

where the second has less alignment required.  If we had explicit alignment
support in the IR, we could handle this case, but we can't until we do.

llvm-svn: 23960

more effective at promoting these allocations, catching them earlier in the
compile process.

llvm-svn: 23959

llvm-svn: 23958

GCC 4.1.  I tried it with 4.0 and 3.3 and it seems fine.

llvm-svn: 23957

llvm-svn: 23956

llvm-svn: 23955

llvm-svn: 23954

llvm-svn: 23953

in the future, remove it.

llvm-svn: 23952