Changes

[NFC][InstCombine] Add tests that show a number of canonicalization
opportunities
Reviewers: spatel, RKSimon, lebedev.ri, apilipenko
Reviewed-By: apilipenko
Tags: #llvm
Subscribers: llvm-commits
Differential Revision: https://reviews.llvm.org/D68263

[lldb] Check if we actually have a Clang type in
ObjCLanguage::GetPossibleFormattersMatches
We call IsPossibleDynamicType but we also need to check if this is a
Clang type, otherwise other languages with dynamic types (like Swift)
might end up being interpreted as potential Obj-C dynamic types.

[lldb][NFC] Remove unused CompilerType::IsPossibleCPlusPlusDynamicType
Reviewers: davide, xiaobai
Reviewed By: davide, xiaobai
Subscribers: davide, JDevlieghere, lldb-commits
Tags: #lldb
Differential Revision: https://reviews.llvm.org/D70074

[lldb][NFC] Move LLVM RTTI implementation from enum to static ID
variable
Summary: swift-lldb currently has to patch the ExpressionKind enum to
add support for Swift expressions. If we implement LLVM's RTTI with a
static ID variable instead of a centralised enum we can drop that patch.
Reviewers: labath, davide
Reviewed By: labath
Subscribers: JDevlieghere, lldb-commits
Tags: #upstreaming_lldb_s_downstream_patches, #lldb
Differential Revision: https://reviews.llvm.org/D70070

[lldb] Add missing include to ObjCLanguage.cpp to fix build

[clang-format] [PR36294] AlwaysBreakAfterReturnType works incorrectly
for some operator functions
Summary: https://bugs.llvm.org/show_bug.cgi?id=36294
Addressing bug related to returning after return type not being honoured
for some operator types.
```
$ bin/clang-format --style="{BasedOnStyle: llvm,
AlwaysBreakAfterReturnType: TopLevelDefinitions}" /tmp/foo.cpp class Foo
{ public:
 bool operator!() const;
 bool operator<(Foo const &) const;
 bool operator*() const;
 bool operator->() const;
 bool operator+() const;
 bool operator-() const;
 bool f() const;
};
bool Foo::operator!() const { return true; } bool Foo::operator<(Foo
const &) const {
 return true;
} bool Foo::operator*() const { return true; } bool Foo::operator->()
const { return true; } bool Foo::operator+() const {
 return true;
} bool Foo::operator-() const {
 return true;
} bool Foo::f() const {
 return true;
}
```
Reviewers: mitchell-stellar, klimek, owenpan, sammccall, rianquinn
Reviewed By: sammccall
Subscribers: merge_guards_bot, cfe-commits
Tags: #clang-format, #clang-tools-extra, #clang
Differential Revision: https://reviews.llvm.org/D69573

[X86] Add more add/sub carry tests
Preparation for: https://reviews.llvm.org/D70079
https://reviews.llvm.org/D70077

DWARFDebugLoclists: add location list "interpretation" logic
Summary: This patch extracts the logic for computing the "absolute"
locations, which was partially present in the debug_loclists dumper,
completes it, and moves it into a separate function. This makes it
possible to later reuse the same logic for uses other than dumping.
The dumper is changed to reuse the location list interpreter, and its 
format is changed somewhat. In "verbose" mode it prints the "raw" value 
of a location list, the interpreted location (if available) and the 
expression itself. In non-verbose mode it prints only one of the 
location forms: it prefers the interpreted form, but falls back to the
"raw" format if interpretation is not possible (for instance, because we 
were not given a base address, or the resolution of indirect addresses 
failed).
This patch also undos some of the changes made in D69672, namely the 
part about making all functions static. The main reason for this is that 
I learned that the original approach (dumping only fully resolved 
locations) meant that it was impossible to rewrite one of the existing 
tests. To make that possible (and make the "inline location" dump work 
in more cases), I now reuse the same dumping mechanism as is used for 
section-based dumping. As this required having more objects know about 
the various location lists classes, it seemed like a good idea to create 
an interface abstracting the difference between them.
Therefore, I now create a DWARFLocationTable class, which will serve as 
a base class for the location list classes. DWARFDebugLoclists is made 
to inherit from that. DWARFDebugLoc will follow.
Another positive effect of this change is that section-based dumping 
code will not need to use templates (as originally) envisioned, and that 
the argument lists of the dumping functions become shorter.
Reviewers: dblaikie, probinson, JDevlieghere, aprantl, SouraVX
Subscribers: hiraditya, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D70081

[lldb][NFC] Simplify a return in
ThreadPlanStepInRange::DefaultShouldStopHereCallback
We know should_stop_here is false here, so we might as well return false
directly.