[InstCombine] Fix infinite loop in demanded FP-class simplification (#230544)
SimplifyDemandedFPClass can recurse through a phi and revisit the same
operand before the outer call returns. In the test, the inner call
replaces the fmul's select operand with the phi.
The outer call then gets the original select back from
SimplifyDemandedUseFPClass, which returns it to indicate an in-place
change. Writing that select back undoes the inner call's replacement and
causes InstCombine to loop.
If NewVal == V but the operand has already changed, keep the replacement
made by the inner call.
Assisted-by: OpenAI Codex
py-prettytable: updated to 3.19.0
3.19.0
Changed
Drop support for EOL Python 3.10
Fixed
Fix copy() failing when a format option is set
Handle rows with fewer cells than header in from_html()
py-pyperf: updated to 2.11.0
2.11.0 (2026-11-08)
* Feature: Add ``--in-process`` option to run benchmarks in the current process.
This is useful when you cannot spawn child processes, such as on WASM environments.
* Feature: Add a new ``tachyon`` hook to profile benchmarks with the Tachyon
sampling profiler of Python 3.15 (``--hook tachyon``).
* Feature: Hooks can now be registered from code with the new ``hooks``
parameter of :class:`Runner`.
* Feature: Add :meth:`Runner.is_worker` to guard code which processes
benchmark results in the main process.
* Feature: Add ``cpu_quota`` metadata: the Linux cgroup CPU bandwidth limit of
the process (ex: ``docker run --cpus=2``).
* Bugfix: Allow a ``mem_max_rss`` metadata value of zero.
* Bugfix: ``psutil`` is now optional on the Emscripten platform.
* Optimization: ``format_number()`` and ``_common_metadata()`` are faster.
* Maintenance: ``pyperf`` now requires Python 3.11 or higher.
py-pygit2: updated to 1.21.0
1.21.0 (2026-11-04)
- Add support for Python 3.15
- New `Config` subclasses: `DefaultConfig` for the default configuration and
`RepositoryConfig` for repository configurations
- Fix `ConfigEntry` retaining `git_config_entry` pointers owned by config
iterators, which could make entry values change unexpectedly and cause
crashes; values are now copied eagerly
- Fix custom ODB backends: acquire the GIL when calling back into Python,
and fix `write_cb`'s type argument
- Fix `References.get()`, `Branches.get()`, and the `in` operator on both
collections raising `InvalidSpecError` for invalid names; they now return
`None` and `False` respectively, as documented
- Fix `sh build.sh stubtest`
- Wheels: Build the bundled libgit2 and libssh2 in Release mode instead of Debug
- Wheels: Update OpenSSL to 3.5.9
[SandboxVec][LoadStoreVec] Support mixed-type load vectorization
Remove the restriction that every load in a top-level load chain must have the vector's element type. A chain of mixed types such as {i32, float} or {double, i32, i32} is loaded as a vector of integers (as chosen by VecUtils::getCombinedVectorTypeFor()), each original load is unpacked from the lanes it occupies, and then reinterpreted back to its own type with SameSizeReinterpret::reinterpretValue().
Chains involving a non-integral pointer are left alone, since such a pointer cannot be recovered from an integer lane.
SameSizeReinterpret is also used by createConstantVector() to pack constants of mixed types into a constant vector.
Co-authored-by: Cursor <cursoragent at cursor.com>
[SandboxVec][LoadStoreVec] Rename ScalarConstReinterpret to SameSizeReinterpret (NFC)
The class reinterprets the bits of a value as another type of the same size. It is used to pack constants in createConstantVector(), and will also be used to unpack loads of mixed types, so the name ScalarConstReinterpret no longer describes it. The class comment and the reinterpretConstant() comment are updated to match.
Co-authored-by: Cursor <cursoragent at cursor.com>
[AMDGPU] Preserve noclobber after acquire operations from a different addrspace
Follow-up to #219991 to address reviewer comments:
AMDGPUAnnotateUniformValues should annotate uniform global loads as
`!amdgpu.noclobber` if the memory they are reading is never clobbered (since
kernel launch) before the load is executed.
PR #219991 strengthened the logic to consider acquire operations before the
load as clobbering (because they cause stores from other threads to be observed
by the load without a data race).
This PR weakens this criterion to ignore acquire operations that don't affect
the global address space (because they don't affect what the load in question
may or may not see). This addresses the performance-relevant case of s_barriers
with LDS-only fences.
The logic is still overly pessimistic for one-as load acquires, they could also
be ignored when looking for clobbering operations.
Disclaimer: Claude gave review comments and suggestions that I addressed during
[5 lines not shown]
Put the toSIAtomicAddrSpace logic into a table and make it consistent with isExtendedGlobalAddrSpace
With that, the change is no longer NFC, since constant addrspaces and
addrspaces above `MAX_AMDGPU_ADDRESS` now map to `SIAtomicAddrSpace::GLOBAL`
instead of `OTHER`. This means that atomics on these addrspaces are no longer
rejected by SIMemoryLegalizer.
The tests only show differences in the generated ISA for volatile loads from
the constant addrspaces; so far we haven't waited directly after each such
volatile load, with this change we do. Arguably, these waits are unnecessary
since the accessed memory is not supposed to change, but, on the other hand,
one could argue that volatile accesses to memory that doesn't change are
pointless in the first place.
[AMDGPU][NFC] Extract SIAtomicAddrSpace and fence MMRA parsing from SIMemoryLegalizer
Determining which memory accesses are ordered by a fence is already
useful in the middle-end; this PR extracts the code to do that from
SIMemoryLegalizer, so that it can be used in middle-end transformations.
So far, unexpected suffix values for the `amdgpu-synchronize-as` were
reported when they were encountered in SIMemoryLegalizer. This PR keeps
that and doesn't report them in the middle end, since that would lead to
a lot of repeated diagnostics for them.
Disclaimer: Claude gave review comments and suggestions that I addressed
during development.
Preparation for ROCM-29879.
Assisted-by: AI