condition was inverted when the code was converted to contains().

llvm-svn: 91295

llvm-svn: 91293

llvm-svn: 91291

the ScalarEvolution pointer into the functions which need it.

llvm-svn: 91289

llvm-svn: 91288

llvm-svn: 91287

former was just exposing a LoopInfoBase implementation detail.

llvm-svn: 91286

llvm-svn: 91284

llvm-svn: 91283

llvm-svn: 91282

SCEVExpander does this automatically.

llvm-svn: 91281

llvm-svn: 91280

llvm-svn: 91278

llvm-svn: 91277

gcc warned that the function may not have a return value, indeed
for non-intel and non-amd X86 CPUs it is right (VIA, etc.).

llvm-svn: 91276

llvm-svn: 91275

llvm-svn: 91274

Moved spill weight calculation out of SimpleRegisterCoalescing and into its own pass: CalculateSpillWeights.

llvm-svn: 91273

sent to Bob.

llvm-svn: 91268

llvm-svn: 91260

llvm-svn: 91259

nlewycky's fix to add -rdynamic so the JIT can look symbols up in Linux builds
of the JITTests binary.

llvm-svn: 91250

x86 CPU detection for the X86 getHostCPUName too, and create a simple
getHostCPUName that returns "generic" for all else.

llvm-svn: 91240

about the potential use of these uninitialized members under certain conditions.

llvm-svn: 91239

llvm-svn: 91233

llvm-svn: 91232

llvm-svn: 91230

merging x >u 5 and x <s 20 because it's impossible to implement.

llvm-svn: 91228

llvm-svn: 91226

llvm-svn: 91223

No testcase yet - it seems we're exposing generic codegen bugs.

llvm-svn: 91221

llvm-svn: 91220

llvm-svn: 91219

MSVS2k8 doesn't define __i386__, hence all the CPU detection code was disabled.
Enable it by looking for _MSC_VER.

llvm-svn: 91217

llvm-svn: 91214

defined in the test, and I don't have time tonight to figure it out.

llvm-svn: 91209

supported by emitGlobals, but I don't have a test case for that.

llvm-svn: 91208

namespace llvm" by qualifying their implementations with ::llvm::.

llvm-svn: 91206

just issues an error for the moment. The front end won't yet generate these
intrinsics for ARM, so this is behind the scenes until complete.

llvm-svn: 91200

While scanning through the uses of an alloca, keep track of the current offset
relative to the start of the alloca, and check memory references to see if
the offset & size correspond to a component within the alloca.  This has the
nice benefit of unifying much of the code from isSafeUseOfAllocation,
isSafeElementUse, and isSafeUseOfBitCastedAllocation.  The code to rewrite
the uses of a promoted alloca, after it is determined to be safe, is
reorganized in the same way.

Also, when rewriting GEP instructions, mark them as "in-bounds" since all the
indices are known to be safe.

llvm-svn: 91184