llvm-svn: 92810

Per offline discussion with Doug, don't perform typo correction when we have encountered a fatal error.  On some files that are woefully wrong (missing headers) this can cause a 3x slowdown in some cases when parsing the file.  It makes sense not to perform typo correction in this case because after a fatal error diagnostics will either be suppressed or not really make any sense.

llvm-svn: 92809

for a 'readonly' property. Fixes radar 7427072.

llvm-svn: 92808

llvm-svn: 92807

bottom-up scheduler. We prefer the lower order number.

llvm-svn: 92806

try to evaluate an expression as a constant boolean condition.  This has
the same intended semantics as used in folding conditional operators.

llvm-svn: 92805

llvm-svn: 92804

llvm-svn: 92803

Add C API hook 'clang_getDeclExtent()', which returns the source extent of a declaration.  This implements <rdar://problem/7280072>.

llvm-svn: 92802

llvm-svn: 92801

llvm-svn: 92800

test/CodeGen/X86, as doesn't use -indvars, and it does use
llc -march=x86-64.

llvm-svn: 92799

result in illegal types for the SHL operator.

llvm-svn: 92797

llvm-svn: 92796

llvm-svn: 92795

uses several kinds of opcode values which are not declared within
that enum. This fixes PR5946.

llvm-svn: 92794

llvm-svn: 92793

llvm-svn: 92792

llvm-svn: 92790

llvm-svn: 92789

The only difference is that EvaluateInDifferentType checks to ensure
they are profitable before doing them :)

llvm-svn: 92788

llvm-svn: 92787

llvm-svn: 92786

instructions.  Thumb does not have the restriction that t2 = t+1.

llvm-svn: 92785

llvm-svn: 92784

llvm-svn: 92783

llvm-svn: 92782

llvm-svn: 92781

llvm-svn: 92780

non-inline key function of a class template instantiation, when no key
function is present, the class template instantiation itself was
instantiated with an explicit instantiation declaration (aka extern
template). I'm fairly certain that the C++0x specification gives us
this lattitude, although GCC doesn't take advantage of it.

llvm-svn: 92779

It is enough to give the super registers CR0, CR1, ..., and specifying the
sub-registers as well causes confusion in the liveness computations.

llvm-svn: 92778

llvm-svn: 92777

llvm-svn: 92776

llvm-svn: 92775

llvm-svn: 92774

llvm-svn: 92773

llvm-svn: 92772

llvm-svn: 92771

llvm-svn: 92770

A phi operand that is implicitly defined in a predecessor becomes an undefined
register after phi elimination. This causes a lot of false positives when the
verifier is checking if live-in registers are live-out from all predecessors.

Removing the verifier checks seems like a better solution than insisting on
IMPLICIT_DEF instructions in predecessor blocks.

llvm-svn: 92769