Use VoidTy instead, to be properly conservative.

llvm-svn: 66463

of an instruction into a helper function.

llvm-svn: 66460

have to be done twice.

llvm-svn: 66449

llvm-svn: 66446

before it does any processing.

llvm-svn: 66443

hopefully no functionality change.

llvm-svn: 66398

a vector type instead of into an integer type.

llvm-svn: 66368

memcpy/memmove'd into or out of.  This fixes a serious
perf issue that Nate ran into.

llvm-svn: 66366

instead of a Constant*, which is what the clients of it really want.

llvm-svn: 66364

parent between MemCpyInst and MemMoveInst, simplify some code to
use it.

llvm-svn: 66361

Lennart Augustsson!

llvm-svn: 66272

llvm-svn: 66262

llvm-svn: 66252

their main routines.  This makes the tools print their argc/argv
commands if they crash.

llvm-svn: 66248

llvm-svn: 66245

llvm-svn: 66244

This is needed so debug info doesn't change codegen.

llvm-svn: 66235

llvm-svn: 66227

llvm-svn: 66140

codegen.  I convinced myself it was OK to skip all
pointer bitcasts here too.

llvm-svn: 66122

llvm-svn: 66115

had 2 uses instead of 1.

llvm-svn: 66112

was causing llvm-gcc to fail to build.  I've
verified it bootstraps now; good enough for me.

llvm-svn: 66073

llvm-svn: 66065

immediately obvious.

llvm-svn: 66062

llvm-svn: 66055

llvm-svn: 66054

onto element accesses.

llvm-svn: 66053

per Chris' suggestion.  Slightly faster.

llvm-svn: 65999

when counting work; it was only off by 1.

llvm-svn: 65993

feed into llvm.dbg.declare nodes, as well as
the debug directives themselves.

llvm-svn: 65976

use, check also for the case where it has two uses,
the other being a llvm.dbg.declare.  This is needed so
debug info doesn't affect codegen.

llvm-svn: 65970

llvm-svn: 65960

llvm-svn: 65945

and put @file directives on their own comment line.

llvm-svn: 65920

(lest they affect codegen).

llvm-svn: 65915

info with it.
Don't count debug info insns against the scan maximum
in FindAvailableLoadedValue (lest they affect codegen).

llvm-svn: 65910

If branch conditions' one successor is dominating another non-latch successor then this loop's iteration space can not be restricted. In this example block bb5 is always executed.

llvm-svn: 65902

clean up when using variable length arrays in llvm-gcc.

llvm-svn: 65832

testsuite:

Running /Volumes/Sandbox/Buildbot/llvm/full-llvm/build/llvmCore/test/CodeGen/X86/dg.exp ...
FAIL: /Volumes/Sandbox/Buildbot/llvm/full-llvm/build/llvmCore/test/CodeGen/X86/nancvt.ll
Failed with exit(1) at line 2
while running: grep 2147027116 nancvt.ll.tmp | count 3
count: expected 3 lines and got        0.
child process exited abnormally
FAIL: /Volumes/Sandbox/Buildbot/llvm/full-llvm/build/llvmCore/test/CodeGen/X86/vec_ins_extract.ll
Failed with exit(1) at line 1
while running:  llvm-as < /Volumes/Sandbox/Buildbot/llvm/full-llvm/build/llvmCore/test/CodeGen/X86/vec_ins_extract.ll |  opt -scalarrepl -instcombine |   llc -march=x86 -mcpu=yonah | not /usr/bin/grep sub.*esp
      subl      $28, %esp
      subl      $28, %esp
child process exited abnormally

And more.

llvm-svn: 65758