[SCCP] Avoid markConstant() in more places (#206494)
This extends the fix from 991455e69e93c0ce88e927eddd28a9ab34d1f8b2 to
two more places. In both of these, we can run into the same situation
where we first mark as constant with a vector that has poison values,
and then again without poison elements, resulting in an assertion
failure.
(An alternative would be to change markConstant() to allow calls with
different constant if the new constant is a vector that only refines
some previously poison elements?)
[AArch64][InstCombine] Combine add with [su]adalp intrinsics (#204796)
It can happen that the [su]adalp uses a zero accumulator and its result
is used as an operand into an ADD instruction. We can fold those.
add(adalp(%pred, zeroinitializer, %in), %acc)
-->
adalp(%pred, %acc, %in)
Upload man pages with attestation (#204852)
This first uploads the man pages as a workflow artifact. Then in another
job which requires more permissions than we want to give to the build
job, the man pages are uploaded as a release asset with attestation.
[X86] Sync scalar hadd/hsub tests between the middle-end and backend (#207163)
Update some more PhaseOrdering/CodeGen test pairs to ensure we're testing what the backend will actually see
Help towards #143000
[analyzer] Rename z3 constraint manager backend to unsupported-z3 (#205370)
The Z3 constraint manager backend (selected via
-analyzer-constraints=z3) is unmaintained and known to crash on
real-world input. Rename the user-facing flag to unsupported-z3 and
reword its description so users see up front that the backend is
unsupported and crash-prone -- patches welcome, crash reports are not.
Assisted-By: claude
[LLD][COFF] Factor out addObjectFile (NFC) (#206811)
Avoid parsing the input COFF file twice: first, implicitly, in
findBitcodeInObject and later when creating the ObjFile instance. Create
the COFFObjectFile earlier and use it for both the findBitcodeInObject
call and ObjFile creation. It's also preparation for handling hybrid
ARM64X object files.
[offload] check olInit and olShutDown error in unittests initialisation (#206764)
if olInit fails, it leaves liboffload in an inconsistent state (proper
cleanup will be addressed in a follow-up patch). This can lead to
seemingly unrelated test failures (e.g. the host device is missing).
This patch makes such tests fail immediately with a clear error message.