evdev: Drop comments from input-event-codes.h
They were copied intact from the Linux GPL-only file.
Requested by: imp, glebius
MFC after: 1 week
(cherry picked from commit 89aa8a94053fdd22ed716fdf424a2d10e70b3188)
[clang][Driver][SPIRV][ClangLinkerWrapper] Pass --allow-partial-linkage to spirv-link (#181870)
Without this flag a lot of tests error in the linker.
---------
Signed-off-by: Nick Sarnie <nick.sarnie at intel.com>
[lldb][windows] release the ConPTY instead of copying its reference (#181811)
When running multiple targets in lldb, the `ProcessLaunchInfo` instance
gets re-used. This is a problem for the ConPTY instance which is owned
by `launch_info` because, when creating a second target, we close and
reopen the `m_pty` of the first target.
This patch replaces the `GetPTYSP` method with `ReleasePTY`, which moves
the `std::shared_ptr` out of `launch_info` instead of creating a new
`std::shared_ptr`. The `m_pty` instance is moved into the target's
process. This way, each target's `Process` instance owns its PTY
instance and is responsible for closing it.
---------
Co-authored-by: Adrian Prantl <adrian.prantl at gmail.com>
[SPIRV] Prevent BB start emission for service functions (#178776)
When working with function pointers, the backend service functions might
still retain call instructions to the original functions. This PR skips
BB start emission for such cases.
[lldb-dap] Validate utf8 protocol messages. (#181261)
I ran into this while debugging a different issue, but when we calcualte
the 'value' field of a variable we were not ensuring the contents were
valid utf8. If assertions are enabled then llvm::json::Value will assert
that the string contains invalid utf8.
To address this I added a wrapper type (`lldb_dap::protocol::String`)
that can be used as a thin wrapper around `std::string` to ensure a
field contains valid utf8. This is now used throughout the
`lldb_dap::protocol::*` types.
devel/py-evalidate: import py-evalidate-2.1.3
Evalidate is simple python module for safe and very fast eval()'uating
user-supplied (possible malicious) Python expressions.
Fix a regression with the v6 IP aliases on PPPoE interfaces (with if_pppoe).
Without this change no v6 aliases can be added to the interface.
Ticket: #16594
[flang][cuda] Fix return value for CUFSetDefaultStream (#181884)
The interface return an integer value but the entry point and lowering
were missing it.
[AMDGPU] Constrain register class during COPY elimination based on their uses (#181909)
When a WMMA scale operand (requiring `VCSrc_b32_Lo256`) was an SGPR that
had been copied from a VGPR, the COPY elimination replaced all uses of
the SGPR with the VGPR but failed to constrain the VGPR to
`vgpr_32_lo256`. This allowed the register allocator to assign a VGPR >=
256 (e.g., $vgpr309), violating the hardware encoding requirement.
