In D65784#1616118, @jasonmolenda wrote:

Yeah, it's not currently hooked up to anything; I'm returning to remote-platform testing soon, if we've lost some necessary functionality I can re-add it, but this option right now isn't doing anything.

complete the corresponding test for extra launchCommands

In D64767#1587311, @labath wrote:

Whether a lot of these tests (e.g. all watchpoint related tests) pass or fail may depend on the exact android device you are running the tests against. However, you are the only ones running android tests ATM, so that does not matter much right now. If that ever changes, we'll have to do something smarter here...

In D64769#1587318, @labath wrote:

The change is fine, but for my own education, could you elaborate on what this "delayed calculation" is, and how does it make the test fail?

add more context to diff

added method skipIfTargetAndroid

allow SysV_x86_64 ABI to handle unknown OS type
this should fix the test SymbolFile/DWARF/debug_loc.s

@labath Hi, you're right about the lld, it didn't make the test pass, instead it became unsupported.

the OS check in SysV x64 ABI broke the test SymbolFile/DWARF/debug_loc.s
added a restriction lld to #REQUIRES

complete the code for floating point registers and cleaned up
the support for floating point registers fixed TestRegistersIterator update the testcased

Added support for XMM registers.
Now the step out on a function returns floating point number should have the right value.
To play with it, define a function

float getFloat(float value) {
    return value;
}

set a break point and step out
LLDB will print out the right value if debugging on Windows-x86_64

Update the GetReturnValueObjectImpl using function CanPassInRegisters to explicitly check

1. Limit the TestReturnValue for nested struct and class (cpp support) to only x86_64
2. This patch somehow fix the bug: pr36870 for Systerm V ABI (windows is waiting for this change to go in). So I change the test to allow passing on SysV-x86_64

D62772 toke care of this

fix switch statement

small update :)

added a virtual function CanPassInRegister in TypeSystem class
to provide info about type can be passed in register or not
ClangASTContext will refer to clang::RecordDecl::canPassInRegister for this info
and later SwiftASTContext can provide the equivalent
updated the test to test on C++
and provided class test, including base class, subclass, abstract class (this one must be in memory)

In D62702#1525655, @compnerd wrote:

Actually, I think that we should extend CompilerType and TypeSystem to expose Clang's knowledge of whether a type is passed in a register by means of using clang::RecordDecl::isPassInRegisters

simplify the method in 'FlattenAggregateType'
added test for nested struct returned in registers

@jingham working on the unit test rn. will upload soon

update the CreateDefaultUnwindPlan.
return false or give empty Unwind Plan may cause lldb to crash and break tests on windows.
So for now, copy the SysV-x86_64

update nit

update a new version based on comment.
cleaned some useless comment
change to use CHAR_BIT for readability