their own .cpp file and make the interpretation
of its flags private.

llvm-svn: 119319

llvm-svn: 119318

branches to be emitted as:

 	bne cr0, 2
instead of:
 	bne cr0, $+8

llvm-svn: 119317

llvm-svn: 119316

llvm-svn: 119315

'db', 'ib', 'da') instead of having that mode as a separate field in the
instruction. It's more convenient for the asm parser and much more readable for
humans.
<rdar://problem/8654088>

llvm-svn: 119310

llvm-svn: 119309

llvm-svn: 119308

these instructions to be encoded with getMachineOpValue.
This unbreaks ExecutionEngine/2003-01-04-ArgumentBug.ll 
when running on a G5

llvm-svn: 119307

Use amazing new function call technology instead of writing identical code in
multiple places.

This fixes PR8604.

llvm-svn: 119306

The live range of a register defined by an early clobber starts at the use slot,
not the def slot.

Except when it is an early clobber tied to a use operand. Then it starts at the
def slot like a standard def.

llvm-svn: 119305

llvm-svn: 119304

llvm-svn: 119303

llvm-svn: 119302

to create the special Neon vector types.  These are intended to be used in
Clang's version of <arm_neon.h> to define special Neon vector types that will
be mangled according to ARM's ABI.

llvm-svn: 119301

This is needed for Neon types when it is most natural to define them in terms
of a typedef.  For example, Neon poly8_t is a typedef for "signed char", and
we want to define polynomial vectors as vectors of that typedef.  Without this
change, the result will be a generic GCC-style vector.  I think this is safe
for other vector types as well, but I would appreciate a review of this.

llvm-svn: 119300

one of the special Neon types.  We'll check for invalid Neon vectors when
they are created, so there's no point in handling them when mangling.

llvm-svn: 119299

llvm-svn: 119298

llvm-svn: 119297

llvm-svn: 119295

Fixes PR8608.

llvm-svn: 119293

llvm-svn: 119290

certain internal type-checking procedures as well as for representing
certain implicitly-generated operations.  Uses to follow.

llvm-svn: 119289

Adds a README for the Clang static analyzer to document its design and work flow.  The contents are taken from email notes by kremenek and xuzhongxing.

llvm-svn: 119288

llvm-svn: 119287

llvm-svn: 119286

caching global code-completion results. In particular, don't perform
either operation the first time we parse, but do both after the first
reparse. 

llvm-svn: 119285

Remove invalid assertion from CFG builder.  When building the CFG pieces for a ternary '?' expression,
it is possible for the confluence block to only have a single predecessor due to calls to 'noreturn'
functions.  Fixes assertion failure reported in PR 8619.

llvm-svn: 119284

to be broken for other reasons

llvm-svn: 119283

llvm-svn: 119282

Clang currently uses a ridiculous amount of stack space when inlining
this function, which can lead to premature stack overflows.

llvm-svn: 119281

This reverts r119183 which borke the buildbots.

llvm-svn: 119270

llvm-svn: 119187

iterator, not TII->OptimizeCompareInstr.

llvm-svn: 119186

llvm-svn: 119185

pass in the first place and was masked by earlier failures not warning
and aborting the block.

llvm-svn: 119184

The live range of a register defined by an early clobber starts at the use slot,
not the def slot.

llvm-svn: 119183

live ranges for the spill register are also defined at the use slot instead of
the normal def slot.

This fixes PR8612 for the inline spiller. A use was being allocated to the same
register as a spilled early clobber def.

This problem exists in all the spillers. A fix for the standard spiller is
forthcoming.

llvm-svn: 119182

llvm-svn: 119181

llvm-svn: 119180