[lldb][tests] Automatically call compute_mydir (NFC)Eliminate boilerplate of having each test manually assign to `mydir` by calling`compute_mydir` in lldbtest.py.Differential Revision: https://r
[lldb][tests] Automatically call compute_mydir (NFC)Eliminate boilerplate of having each test manually assign to `mydir` by calling`compute_mydir` in lldbtest.py.Differential Revision: https://reviews.llvm.org/D128077
show more ...
[lldb] [test] Update baseline test status for FreeBSDFixes #19721Fixes #18440Partially fixes bug #47660Fixes #47761Fixes #47763Sponsored by: The FreeBSD Foundation
[lldb] Only promote -Wignored-attributes to an errorAvoid other warnings from failing the test, such as-Wunused-command-line-argument in the downstream Swift fork.
Skip tests on older versions of clang
[lldb] Skip TestCCallingConventions.test_ms_abi on arm64rdar://84528755
[lldb] Add support for DW_AT_calling_convention to the DWARF parserThis adds support for parsing DW_AT_calling_convention in the DWARF parser.The generic DWARF parsing code already support extrac
[lldb] Add support for DW_AT_calling_convention to the DWARF parserThis adds support for parsing DW_AT_calling_convention in the DWARF parser.The generic DWARF parsing code already support extracting this attribute from ADIE and TypeSystemClang already offers a parameter to add a calling conventionto a function type (as the PDB parser supports calling convention parsing), sothis patch just converts the DWARF enum value to the Clang enum value and adds afew tests.There are two tests in this patch.:* A unit test for the added DWARF parsing code that should run on all platforms.* An API tests that covers the whole expression evaluation machinery by tryingto call functions with non-standard calling conventions. The specific subtestsare target specific as some calling conventions only work on e.g. win32 (or, ifthey work on other platforms they only really have observable differences on aspecific target). The tests are also highly compiler-specific, so if GCC orClang tell us that they don't support a specific calling convention then we justskip the test.Note that some calling conventions are supported by Clang but aren't implementedin LLVM (e.g. `pascal`), so there we just test that if this ever getsimplemented in LLVM that LLDB works too. There are also some more tricky/obscureconventions that are left out such as the different swift* conventions, someplanned Obj-C conventions (`Preserve*`), AAPCS* conventions (as the DWARF->Clangconversion is ambiguous for AAPCS and APPCS-VFP) and conventions only used forOpenCL etc.Reviewed By: aprantlDifferential Revision: https://reviews.llvm.org/D108629