llvm-svn: 119462

should get the submode from the load/store multiple instruction's opcode.

llvm-svn: 119461

instructions have to distinguish between lists of single- and double-precision
registers in order for the ASM matcher to do a proper job. In all other
respects, a list of single- or double-precision registers are the same as a list
of GPR registers.

llvm-svn: 119460

class, uses DominatorTree which is an analysis.  This change moves all of
the tricky hasConstantValue logic to SimplifyInstruction, and replaces it
with a very simple literal implementation.  I already taught users of
hasConstantValue that need tricky stuff to use SimplifyInstruction instead.
I didn't update InlineFunction because the IR looks like it might be in a
funky state at the point it calls hasConstantValue, which makes calling
SimplifyInstruction dangerous since it can in theory do a lot of tricky
reasoning.  This may be a pessimization, for example in the case where
all phi node operands are either undef or a fixed constant.

llvm-svn: 119459

While there, add a note about an inefficiency I noticed.

llvm-svn: 119458

rather than hasConstantValue.

llvm-svn: 119457

systematically, CollapsePhi will always return null here.  Note
that CollapsePhi did an extra check, isSafeReplacement, which
the SimplifyInstruction logic does not do.  I think that check
was bogus - I guess we will soon find out!  (It was originally
added in commit 41998 without a testcase).

llvm-svn: 119456

This fixes some extreme compile times on unrolled sha512 code.

llvm-svn: 119455

llvm-svn: 119454

with the Interrupted bit set.  Process::HandlePrivateEvent ignores Interrupted events.
DoHalt is changed to ensure that the stop even is processed, and an event with
the Interrupted event is posted.  Finally ClangFunction is rationalized to use this
facility so the that Halt is handled more deterministically.

llvm-svn: 119453

'SizeOfAlignOfExpr' and 'CXXSCalarValueInitExpr'
to data-recursion algorithm.

llvm-svn: 119452

  @synthesize foo = _foo;

keep track of the location of the ivar ("_foo"). Teach libclang to
visit the ivar as a member reference.

llvm-svn: 119447

operands in a variadic instruction.

llvm-svn: 119446

output from clang and llvm-gcc compiled program; both generate the correct debug
info with respect to the typedef scoped inside a namespace.

Add a TestBase.getCompiler(self) method which returns the compiler in effect the
test suite is now running with.  Subclasses (like TestNamespace) can use it to
distinguish among different compilers.

llvm-svn: 119445

data-recursion algorithm.

llvm-svn: 119444

to data-recursion algorithm.

llvm-svn: 119443

explicit template args within data-recursion
algorithm.

llvm-svn: 119442

AddrLabelExpr to data-recursion algorithm, and
unify that reasoning with GotoStmt.

llvm-svn: 119441

VAArgExpr to data-recursion algorithm.

llvm-svn: 119440

CXXTypeidExpr to data-recursion algorithm.

llvm-svn: 119439

TypesCompatibleExpr to data-recursion algorithm.

llvm-svn: 119438

llvm-svn: 119437

llvm-svn: 119436

"getRegisterListOpValue" logic. If the registers are double or single precision,
the value returned is suitable for VLDM/VSTM.

llvm-svn: 119435

I mistakenly thought that this was checking for vector name mangling, but
it is not.  Since we're no longer wrapping Neon vectors in structs, this
test can just return a vector directly.  There are already other tests for
that, so just to make this interesting, change the test to return a struct
of two vectors.

llvm-svn: 119434

llvm-svn: 119433

llvm-svn: 119425

about a __block cxx object.

llvm-svn: 119411

we were just getting a range covering only the property name, which is
certainly not correct (and broke token annotation, among other
things). 

Also, teach libclang about the relationship between
@synthesize/@dynamic and @property, so we get property name and
cursor-reference information for @synthesize and @dynamic.

llvm-svn: 119409

branches.  Fixes PR8623.

llvm-svn: 119408

yet hooked up to anything yet.

llvm-svn: 119407

llvm-svn: 119406

llvm-svn: 119405

No functional change.

llvm-svn: 119404

llvm-svn: 119403

case based on CodeGen/volatile-1.c which tests the current C++
semantics, and note the many, many places we fall short of them.

llvm-svn: 119402

a different pass, the complicated interaction between cmov expansion
and fast isel is no longer a concern.

llvm-svn: 119400

This is not to be used during normal test suite run, but to be used to stress test
specific test sequences repeatedly.

Example:

./dotest.py -# 3 -v breakpoint_conditions

will repeat the test suite 3 times for tests under the breakpoint_conditions directory.

llvm-svn: 119399

though possibly not a good idea.

llvm-svn: 119398

llvm-svn: 119397