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

llvm-svn: 119396

llvm-svn: 119395

Patch by Louis Zhuang!

llvm-svn: 119394

llvm-svn: 119393

llvm-svn: 119391

llvm-svn: 119390

llvm-svn: 119389

increased.  The following program is running 49% faster:

#include <iostream>
#include <memory>
#include <chrono>
#include <vector>
#include "chrono_io"

int main()
{
    typedef std::chrono::high_resolution_clock Clock;
    Clock::time_point t0 = Clock::now();
    {
        std::shared_ptr<int> p(new int (1));
        std::vector<std::shared_ptr<int> > v(1000000, p);
        v.insert(v.begin(), p);
        v.insert(v.begin(), p);
        v.insert(v.begin(), p);
        v.insert(v.begin(), p);
    }
    Clock::time_point t1 = Clock::now();
    std::cout << (t1-t0) << '\n';
}

llvm-svn: 119388

llvm-svn: 119387

llvm-svn: 119386

llvm-svn: 119385

Next: Add support for the !HasDotLocAndDotFile case to the MCAsmStreamer
and then switch codegen to use it.

llvm-svn: 119384