[CalledValuePropagation] Fix non-deterministic metadata generation (#244837)
Fixes non-deterministic metadata numbers in CVP outputs.
Non-deterministic numbers in CVP outputs make it difficult to trace when
and how two compilations (with two versions of the compiler) start to
diverge by tracing `-print-after-all` outputs.
To repro: copy sqlite3.c from llvm-test-suite and optimize with `opt -O3
-print-after-all -ir-dump-directory=...` and save the outputs of a few
runs in different directories. The outputs start to diverge after CVP
before this change. With this change we reliably get identical IRs
throughout the pipeline.
mail/stalwart-proxy: Update 1.0.5 => 2.0.0
Changelog:
https://github.com/stalwartlabs/proxy/blob/v2.0.0/CHANGELOG.md
- Follow the new upstream default layout: certs/, mappings/mappings.tsv
and admin-token.
- The configuration directory is now owned by the stalwart-proxy user,
so the new management WebUI can rewrite config.toml and store uploaded
certificates, and "stalwart-proxy init" can provision a minimal setup.
- Drop the test skips: the unit tests moved out of the source tree.
PR: 300990
[AMDGPU] Keep soft waitcnts unchanged until SIInsertWaitcnts converges
On the first visit to a loop header only the preheader state is known.
A soft waitcnt there (e.g. from a release fence) can have some of its
counters simplified away while another counter keeps the instruction
alive: the fence's own vmcnt(0), a preceding wait.asyncmark, or an
explicit s_waitcnt. The soft waitcnt was then rewritten with the
simplified value and promoted to a hard waitcnt, or merged into a
preceding hard one. When the back edge later brought a pending LDS
store, the original lgkmcnt(0) request was gone, and the s_barrier after
the release fence no longer waited for it.
Treat soft waitcnts as requests that depend on the incoming state: never
merge, promote or rewrite them while the analysis iterates. They are
kept unchanged in DeferredErasures, a hard waitcnt (existing or new)
carries what is needed on each visit, and the soft waitcnts are erased
once the analysis converges. This extends #220357, which did the same
only for soft waitcnts that were simplified away entirely.
[11 lines not shown]
[AMDGPU][NFC] Pre-commit tests for soft waitcnt requests lost at a loop header (#244686)
Two cases where a soft waitcnt at a loop header loses its `lgkmcnt(0)`.
On the first visit to the header no LDS operation is pending yet, so the
soft waitcnt's `lgkmcnt` is simplified away, while a `vmcnt` keeps the
instruction alive. That `vmcnt` comes either from the soft waitcnt
itself or from a preceding hard `vmcnt(0)` that it is merged into. The
DS write at the end of the loop is then not waited for before the
`S_BARRIER` on the next iteration.
The checks show the current, incorrect output (`S_WAITCNT .Vmcnt_0`
before `S_BARRIER`).
Assisted-by: Claude Opus 5.5
---------
Co-authored-by: Claude Opus 5.5 <noreply at anthropic.com>
ExpandVariadics: Invalidate function analyses individually
Avoid discarding analyses that never need to be invalidated, such as
TargetLibraryInfo. Clear the analyses of erased functions.
Co-authored-by: Claude Opus 5.5 <noreply at anthropic.com>
AllocToken: Only invalidate analyses of instrumented functions
AllocToken tried to preserve the CFG analyses, but did not preserve the
function analysis manager proxy, so all function analyses were
invalidated.
Co-authored-by: Claude Opus 5.5 <noreply at anthropic.com>
[mlir] Notify rewriter when replacing SCF, Vector and EmitC bodies (#244448)
Fixes a few places where block manipulation was done without notifying
the rewriter.