[Clang][ABI][X86] Fix arg extension incompatibility with platform psABI (#236450)
This resolves a long-standing incompatibility between the argument
passing ABI used by Clang and the platform psABI, primarily for x86-64
SysV targets. The psABI specifies that the caller does not need to
extend small integers, and the callee can make no assumptions about the
high bits. However, Clang instead extended small integers in the caller,
and assumed that the extension is present in the callee.
The platforms affected by this change are:
* x86-32 and x86-64 targets using the SysV ABI, except Darwin and
PlayStation. For Darwin/Playstation, the Clang ABI is now the platform
ABI. (The x86-64 SysV ABI is nowadays very explicit about high bits
being unspecified. On x86-32 SysV this is specified "by omission".)
* x86-32 Windows. I don't believe this has any ABI spec worth
mentioning, but the emergent MSVC behavior seems to be that it performs
extensions in the callee, i.e. does not assume that the high bits are
extended. (This is inherited from the previous version of the patch, so
I'm mostly trusting that it's correct.)
[69 lines not shown]
[RISCV][P-ext] Legalize splat shift amounts during vector lowering (#242996)
Vector legalization can create splat BUILD_VECTOR shift amounts with
illegal scalar operand types. Use `DAG.getSplatValue` with
`LegalTypes=true` to obtain a legal scalar before creating packed shift
nodes.
Fixes #242983
[BOLT][RISCV] Preserve hot fallthrough paths when placing cold jump stubs (#236726)
RISC-V long-jump stubs for cross-fragment edges are currently inserted
immediately after their source blocks, which can interrupt hot
fallthrough paths and force hot execution to branch over cold stubs.
Place stubs for zero-count edges at the end of the source fragment when
the source has a fallthrough successor in the same fragment and a
conservative distance bound fits within the conditional branch range.
This follows BOLT's existing AArch64 strategy of keeping cold
trampolines out of hot paths whenever branch reach permits.
[libc] Move the fork gettid call into a syscall wrapper (#242606)
Move the uncached gettid syscall used by fork() to refresh the child TID
into linux_syscalls::gettid. Register the wrapper in CMake and Bazel.
[DebugInfo] Invalidate debug info of users when an icmp predicate cha… (#238019)
…nges
Fixes https://github.com/llvm/llvm-project/issues/218620
When an `icmp` predicate changes, future calculations using that value
could change. Any debug records relying on the results of those
calculations would then be incorrect.
`CorrelatedValuePropagation` goes through the user chain to see what the
range of values could be, which lets it decide if it can make this
optimisation. This PR changes that so that the debug records of those
users are also collected as it goes through the chain. Then, if the
optimisation is taken, we invalidate those debug records to prevent
incorrect values from being reported.
sound: Remove stale midi module dependencies
midi(4) stopped being a module in 45bb10e0ed5a ("sound: Stop building
midi as a module"), so snd_cmi(4) and snd_emu10k1(4) fail to load
because they still depend on it.
Fixes: 45bb10e0ed5a ("sound: Stop building midi as a module")
Sponsored by: The FreeBSD Foundation
MFC after: 1 day
libm: Implement iseqsig()
C23 adds iseqsig(), the signaling counterpart of ==, which
raises FE_INVALID on any NaN rather than only on signaling
ones (as per §7.12.17.7). The helpers raise it explicitly
instead of relying on relational operators, which the
compiler may emit as quiet comparisons, and the macro
dispatches on float_t so that wider-evaluated arguments
are not narrowed (§F.10.14.1).
Reviewed by: kargl, fuz
Approved by: fuz (mentor)
MFC after: 1 month
Differential Revision: https://reviews.freebsd.org/D60642
[LV] Pre-commit tests for FP derived IV index conversion (NFC) (#240741)
Add a test for an FP induction with a trip count above INT32_MAX, which
is currently miscompiled because the iteration index is converted with
sitofp. Also add an X86 cost test for converting an i64 index of an FP
derived IV.
The fix is in #240743.
Assisted-by: Claude Code
[CIR] Use memory types for bool aggregate constants (#236082)
CIR lowers scalar bool values to `i1`, but bool objects use byte-sized
storage. For example, a `bool[3]` becomes `!llvm.array<3 x i8>`, so its
dense initializer must use `tensor<3xi8>` rather than `tensor<3xi1>`.
Thread the converted element type and module-scoped data layout through
aggregate constant lowering so bool arrays and record members use the
memory type selected by `convertTypeForMemory`. This keeps constant
attributes consistent with their LLVM container types and retains bool's
`i1` value representation.
---------
Co-authored-by: Steffen Larsen <sholstla at amd.com>
[Support] Grow bump allocator slabs faster (#243000)
Reduce the default slab growth delay from 128 to 8, retaining 4 KiB
initial slabs.
On CTMark (-march=rva23u64 -O3), median user CPU time drops by
0.11% and peak RSS geomean by 1.96%.
Assisted-by: TRAE CLI (GPT-6)
[AMDGPU] Treat a bitcast between legal types or same-size scalars as free (#238412)
The generic cost model treats a bitcast as free only when both types are
integer types or both are not. AMDGPU keeps integer and floating-point
values in the same registers, so a bitcast between two legal types is a
no-op. A scalar bitcast from i32 to float cost 1, but the vector bitcast
from <2 x i32> to <2 x float> cost 0. The SLP vectorizer counted this
difference as a saving.
A bitcast between two scalars that are legalized to types of the same
size, such as i16 and half without 16-bit instructions, is free as well.
A bitcast that involves a legalized vector, such as a vector of i8,
keeps its cost, because the lanes may need repacking.
Assisted-by: Claude Opus
[SCEV] Look up loop guard rewrites in a single place (NFC). (#242875)
Look up rewrites for expressions once in ::visit, instead of duplicating
code in each visitor.
Currently still limited to set existing set of nodes. I am planning on
extending this to all expressions, but there are a few regressions I
still need to investigate.
PR: https://github.com/llvm/llvm-project/pull/242875
[flang] Remove redundant parse tree walk for NUMERIC_STORAGE_SIZE warning (#241634)
PR #220779 made `ExpressionAnalyzer::Analyze(const parser::Expr &)` walk
the parse tree of an expression every time it returns a saved typed
expression, to repeat the NUMERIC_STORAGE_SIZE check on the names in it.
`IterativelyAnalyzeSubexpressions` analyzes a chain of operations from
the bottom up, and each operation then asks for its already analyzed
operands again, so each node was visited once per enclosing operation.
That is quadratic in the length of the chain: `-fsyntax-only` on an
assignment whose right-hand side adds 60,000 literal constants takes 27
s without this change and 0.4 s with it.
The walk is not needed when semantic analysis reports no error. The
analysis that saved a typed expression has already called `Analyze(const
parser::Name &)` for each name in it, and the warning is added to the
`SemanticsContext` message buffer directly, so contextual message
discarding does not affect it. This change removes the walk and its
visitor.
[5 lines not shown]
py-hanko: updated to 0.38.1
0.38.1
Bugs fixed
Addressed another scenario where xref parsing entered infinite loops on crafted input.
Ensure legacy xref table parsing correctly rejects cases where the same object occurs multiple times in the same section. This adversely affected difference analysis.
py-setuptools-git-versioning: updated to 3.2.2
3.2.2
Bug Fixes
Fixed {timestamp}, {timestamp:} and {timestamp:%s} substitutions failing on Windows with ValueError: Invalid format string.
%s is not supported by strftime on every platform, so the unix timestamp is now computed directly.
py-django-reversion: updated to 6.5.2
6.5.2 - 2026-11-12
- Fixed permission checks in ``VersionAdmin`` when reverting or recovering an object. Permissions are now checked against the current object before the revert runs, and revisions are limited to the admin's own model (@Shin--, @etianen).
py-django-import-export: updated to 4.4.5
4.4.5
Fixed the import_id_fields error messages not being translated, because the column names were interpolated before the message was passed to gettext. Added the Spanish translation of both messages (2219)
[flang] Add SELECT CASE lowering tests for INTEGER(16) ranges and UNSIGNED(16) (#242946)
The test added with the SELECT CASE INTEGER(16) fix (#240149) covers
only point case values. The same lowering path also builds the bounds of
ranges (`#fir.interval`, `#fir.lower`, `#fir.upper`) and the case values
of UNSIGNED(16) selectors, which no lowering test covered.
Add an INTEGER(16) range test to `select-case-statement.f90` and an
UNSIGNED(16) test to `unsigned-ops.f90`, with values on both sides of
`2**64` and of the signed maximum `2**127`. Also fix the indentation of
one `CHECK-LABEL`.
Assisted-by: AI