1. [clang] Make signature help work with dependent args (details)
  2. [lldb][NFC] Remove stride parameter from GetArrayElementType (details)
  3. [VE] Support f128 (details)
  4. [lldb] Get lldb-server platform's --socket-file working again (details)
Commit 53c593c2c893a40083771789e3d3e164eea1892d by kadircet
[clang] Make signature help work with dependent args


Differential Revision:
The file was modifiedclang/lib/Sema/SemaCodeComplete.cpp (diff)
The file was modifiedclang/test/CodeCompletion/call.cpp (diff)
The file was modifiedclang-tools-extra/clangd/unittests/CodeCompleteTests.cpp (diff)
Commit 5913f2591c45dc84e872a62343f81462372ccbdb by Raphael Isemann
[lldb][NFC] Remove stride parameter from GetArrayElementType

This parameter isn't used anywhere in LLDB nor the Swift downstream branch. It
also doesn't really fit into the TypeSystem APIs that usually don't return
additional related functionality via some output parameters. Also the
implementations already states that the calculated value there is wrong.

Let's remove it. If we need this functionality at some point then Swift's much
nicer `GetByteStride` function seems like the way to go.

Reviewed By: aprantl

Differential Revision:
The file was modifiedlldb/source/Plugins/TypeSystem/Clang/TypeSystemClang.h (diff)
The file was modifiedlldb/include/lldb/Symbol/TypeSystem.h (diff)
The file was modifiedlldb/source/Plugins/TypeSystem/Clang/TypeSystemClang.cpp (diff)
The file was modifiedlldb/include/lldb/Symbol/CompilerType.h (diff)
The file was modifiedlldb/source/Symbol/CompilerType.cpp (diff)
Commit 40f1e7e80401dab11f6003fb59c43ba9059959cd by marukawa
[VE] Support f128

Support f128 using VE instructions.  Update regression tests.
I've noticed there is no load or store i128 test, so I add them too.

Reviewed By: simoll

Differential Revision:
The file was modifiedllvm/test/CodeGen/VE/store_gv.ll (diff)
The file was modifiedllvm/lib/Target/VE/VEInstrInfo.cpp (diff)
The file was modifiedllvm/test/CodeGen/VE/store.ll (diff)
The file was modifiedllvm/lib/Target/VE/ (diff)
The file was modifiedllvm/lib/Target/VE/ (diff)
The file was modifiedllvm/test/CodeGen/VE/fp_sub.ll (diff)
The file was modifiedllvm/test/CodeGen/VE/fp_div.ll (diff)
The file was modifiedllvm/test/CodeGen/VE/fp_add.ll (diff)
The file was modifiedllvm/lib/Target/VE/VEISelLowering.cpp (diff)
The file was modifiedllvm/test/CodeGen/VE/fp_mul.ll (diff)
The file was modifiedllvm/lib/Target/VE/VEMCInstLower.cpp (diff)
The file was modifiedllvm/test/CodeGen/VE/call.ll (diff)
The file was modifiedllvm/test/CodeGen/VE/load.ll (diff)
The file was modifiedllvm/lib/Target/VE/VEISelLowering.h (diff)
The file was modifiedllvm/test/CodeGen/VE/load_off.ll (diff)
The file was modifiedllvm/lib/Target/VE/VERegisterInfo.cpp (diff)
The file was modifiedllvm/test/CodeGen/VE/load_gv.ll (diff)
The file was modifiedllvm/test/CodeGen/VE/va_caller.ll (diff)
The file was modifiedllvm/test/CodeGen/VE/va_arg.ll (diff)
Commit c57ea1b48f26caf7922bf434187e1c277f412550 by Raphael Isemann
[lldb] Get lldb-server platform's --socket-file working again

`lldb-server platform --socket-file /any/path` currently always fails to create
the socket file.  This stopped working after D67424 which changed the
input variables of `writeFileAtomically` slightly. We're expected to
pass in a temporary path template (`/tmp/foo-%%%%%`) and the final
path we want to write. Instead we currently pass in the never set
`temp_file_path` as the temporary path (which will make this function always
fail) and pass in the temp_file_spec's path as the final path (which is actually
the template path such as `/tmp/foo-%%%%%`) instead of the actual path
we want to write (e.g. `/tmp/foo`).

Reviewed By: labath

Differential Revision:
The file was modifiedlldb/tools/lldb-server/lldb-platform.cpp (diff)