Two emulation patches:
- hw/mc146818rtc.c -- replace previous patch with the one that fixes the
same issue but is more correct by Philippe Mathieu-Daudé (also
being upstreamed).
- m68k/op_helper.c -- In the DIVS.L helper, special case INT_MIN / -1,
which traps on some hosts and crashes Qemu (Qemu issue #2078).
Bump PKGREVISION to 4.
[ADT] Compute end() after removal in llvm::erase and llvm::erase_if (#243189)
Per the C++ Standard, `std::remove` may leave unspecified values in the
removed tail. Visual Studio 2026's vectorized implementation on ARM64
clears a removed singleton pointer, causing `TinyPtrVector` to become
empty and changing its `end()`.
Since the call to the container's `erase()` used both `std::remove` and
`end()` for different arguments, there was no guarantee which order they
will be evaluated. The fix is to split the call to `std::remove` into
its own statement, guaranteeing that it will be evaluated before the
call to `end()`.
Fixes <https://github.com/rust-lang/rust/issues/165953>
[cmake] Add PCH support for the MSVC dylib build (#242637)
Previously, we were always using a single PCH for every target. This was
not compatible with the MSVC/clang-cl LLVM dylib build because we set
different defines depending on whether we are building the LLVM library
or consuming it, and how.
In order to have working PCH for this build configuration, these changes
add a new property to LLVM targets, LLVM_ABI_MODE, which defines how a
target is built and what its PCH mode is. The mode is "none" for build
configurations that only have a single mode. Otherwise, it is one of
"export", "import" or "static".
When a PCH is created for a target in a mode outside of "none", we also
create the other two PCHs, through a static library with an empty TU.
When looking for a PCH to reuse among dependencies, we then check the
PCH mode. In case of a mismatch, we use the appropriate static library's
PCH, if it exists.
[22 lines not shown]
[ConstraintElim] Limit the recursion depth in doesHold (#243985)
Some queries result in nested decompositions, which for deep nests of
adds or subs can grow the stack linearly with the length of the chain,
which impacts compile time, and at worst can blow the stack. The
existing decomposition cache helps mitigate this slightly for cases
where the nested query happens after the operand's decomposeImpl
returns. The new depth limit covers cases where it does not, degrading
the respective results. We store the observed depth at which the results
had to be degraded in order to avoid returning suboptimal results for
later queries of the same value that have more budget.
A depth limit of 32 covers all of the current lit tests prior to this
change. That said, it looks like we can be a lot more conservative with
a limit of 2, since the only test with deep nesting looks like a
synthetic case designed to stress compile time + decomposition caching.
Feel free to bump that up, if needed.
middleware: strengthen path handling
Paths that an unprivileged user may control are opened with safe_open,
safe_open_raw and safe_makedirs from truenas_os_pyutils, which refuse a
symlink anywhere in the path, and a FIFO, socket or device node before
opening it.
- rsync: create and chown ~/.ssh/known_hosts through symlink-refusing fds;
cap the known_hosts read at 4 MiB
- ssh-keyscan: pass "--" before the host
- user: read authorized_keys with safe_open, capped at 1 MiB; unlink it
through a symlink-free .ssh fd
- filesystem.mkdir: chmod, rmdir and listxattr through fds; compare .ssh by component
- NFS: refuse export paths that exportfs would rewrite
- nvmet: a FILE namespace must be a symlink-free regular file in a data pool
- SMB: path_suffix and dataset_naming_schema must stay beneath the share
- filesystem.set_zfs_attributes: callers without FULL_ADMIN are limited to data pools
- ACL and ZFS attribute calls open through safe_open_raw; listdir no longer
opens symlink targets and skips unresolvable links
[6 lines not shown]
RuntimeLibcalls: Add attributes to printf variants
Give the integer-only and size-optimized printf variants the
attributes of the corresponding printf functions.
Co-authored-by: Claude Opus 5.5 <noreply at anthropic.com>
Merge tag 'arm64-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux
Pull arm64 fixes from Catalin Marinas:
"BBML3 allow-list corrections for Cortex-X4 and Neoverse-V3/V3AE
following updated errata, a kCFI oops during kexec relocation and NEON
intrinsics type mismatches causing CRC64 and XOR build failures with
tip-of-tree Clang:
- Remove Cortex-X4 and Neoverse-V3/V3AE from the BBML3 allow list
Updated errata documents show that revisions previously reported as
fixed remain affected by load/store livelocks when changing mapping
sizes without break-before-make
- Fix a kCFI oops during kexec image relocation. Give the relocation
routine a type hash and enter the copied code at the correct offset
- Fix the build with recent Clang versions by removing the stdint.h
type overrides for NEON intrinsics. The CRC64 and XOR intrinsics
[9 lines not shown]
[DebugInfo][FLMD] Add printing support for FLDebugLoc+DIDbgLoc
This patch follows up on the preceding patch by adding support for
printing FLDebugLoc as an attachment `!!dbgLoc(...)` for instructions and
debug records, and for printing DIDbgLoc nodes which contain a !!dbgLoc
operand.
A major component of this patch is the addition of a "DebugLoc conversion"
layer, which allows for conversion between DILocation and FLDebugLoc
formats. This is currently only used for converting DILocation->FLDebugLoc
for printing, but provides a common mechanism that will later be used for
FLDebugLoc<->DILocation conversion for printing+parsing, switching between
the two depending on which format is currently being used in-memory. Due to
the constraint of needing to support consistent conversions at different
points in time (primarily for MIR printing and lazy bitcode
materialization), some information is stored in the LLVMContext, including
a third representation of source location information, stored in a format
which is easy to convert to/from either existing format.
[11 lines not shown]
[CIR][OpenMP] Temporarily report error for OpenMP device code with spirv target (#243989)
An OpenMP device module (`openmp_is_target_device = true` in
`cir.lowering_options`) with some spirv* triples will lead to a crash in
mlir-translate, after `CallConvLoweringPass` for SPIRV.
This isn't an issue in the call-conv lowering for SPIRV itself, but some
missing gaps in MLIR/OpenMP dialect that incorrectly handles OpenMP
device code translation. Therefore, we've decided to temporarily report
error for OpenMP device code with SPIRV target, until MLIR side is
fixed.
Tracking issue: https://github.com/llvm/llvm-project/issues/244021
Merge tag 's390-7.4-2' of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux
Pull s390 fixes from Alexander Gordeev:
- Fix error handling for monitor start and stop operations
Return failures to userspace, prevent inconsistent state
and potential use-after-free scenarios
- Ensure skipped syscalls return -ENOSYS as expected
Preserve existing ptrace behavior while separating syscall
number handling from the return value stored in gpr2
- Fix a race during module initialization where sysfs handlers
could access an uninitialized device list semaphore
* tag 's390-7.4-2' of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux:
s390/dcssblk: Initialize device semaphore before sysfs registration
[2 lines not shown]
[DebugInfo][FLMD] Add printing support for FLDebugLoc+DIDbgLoc
This patch follows up on the preceding patch by adding support for
printing FLDebugLoc as an attachment `!!dbgLoc(...)` for instructions and
debug records, and for printing DIDbgLoc nodes which contain a !!dbgLoc
operand.
A major component of this patch is the addition of a "DebugLoc conversion"
layer, which allows for conversion between DILocation and FLDebugLoc
formats. This is currently only used for converting DILocation->FLDebugLoc
for printing, but provides a common mechanism that will later be used for
FLDebugLoc<->DILocation conversion for printing+parsing, switching between
the two depending on which format is currently being used in-memory. Due to
the constraint of needing to support consistent conversions at different
points in time (primarily for MIR printing and lazy bitcode
materialization), some information is stored in the LLVMContext, including
a third representation of source location information, stored in a format
which is easy to convert to/from either existing format.
[11 lines not shown]
[PowerPC] Require HasPartwordAtomics for l(b|h)arx|st(b|h)cx intrinsics (#242964)
Previously the halfword atomics had an ISA 2.07 predicate and the byte
atomics had none. Group them together under a HasPartwordAtomics
predicate instead.
LLM assistance was used for the test.
search: report an invalid regular expression once
The regular expressions are compiled by the SQL function when the query
runs, so an invalid pattern was reported by the SQL layer, with the name
of an internal file, and once per repository it was applied to.
Check the pattern when the query is created instead: it is now reported
once, as a user error, by every command which matches a pattern as a
regular expression. pkg info also fails instead of reporting the error
and exiting successfully.
Reported in #2751.
upgrade: expand deps of the selected candidate
The upgrade chain can be narrowed to a candidate whose dependencies
have not been seen yet, in particular when a lower-priority repository
still carries an older version of the package. Select the candidate
before expanding the dependencies, as the partial upgrade path already
does.
Fixes: #2761
scripts: add pre-transaction scripts
A package could only check that the system is ready for it from its
pre-install script, which runs in the middle of the transaction: failing
there leaves the system half updated, in a state which cannot be rolled
back.
This script is run early in the transaction, add and register also calls
it.
This would allow to move sanity checks out of *install scripts
search: match a glob-looking pattern as a glob
pkg search matches regular expressions by default, so a pattern like
'*rust' was reported as an invalid regular expression. When no match
mode is requested, match a pattern which looks like a shell glob and
does not compile as a regular expression as a glob instead.
A pattern which is a valid regular expression keeps its meaning, and an
explicitly requested regular expression is still reported as invalid.
Also match the package name and not only the name and the version in the
remote queries, like the local ones do: with a glob or an exact match, a
pattern meant to match the name alone could never match, so '-e rust' and
'-g *rust' found nothing.
Reported in #2751.
edbrowse: Update edbrowse to version 3.8.15
Packaging changes:
Migrate to quickjs-ng
Upstream changes:
The lsr and lsc commands.
Migrate from quickjs to quickjs-ng.
Rerender quickly after browse then throttle back to the rr_interval.
eflite: Update eflite to version 0.0.0.91
Upstream changes:
Keep the audio device open
Fix build with gcc 15
0xa0 is a hard space
Fix the dictionary of high ASCII characters
Run autoupdate
[54 lines not shown]
Don't deallocate the Tx and Rx rings in dwxe_down() and only allocate
them in dwxe_up() if they haven't been allocated already. This avoids
memory allocations that might sleep in DVACT_RESUME.
ok deraadt@
[KnownBits] Share the ctlz upper-bound calculation (#244551)
This is splitting out the refactoring part of #244421 into its own PR.
Move the existing ValueTracking `ctlz` rule into a new `KnownBits::ctlz`
method and use it in SelectionDAG and GlobalISel as well. To preserve
existing behavior, the SDAG/GISel callers don't pass the ZeroIsPoison
flag yet.
LLM disclosure: Astra 6.2 helped me review the PR.
[SPIRV] Enable NSDI features by default for AMD
Enable -spirv-debug-lexical-block-discriminator-scope,
-spirv-debug-scope-forward-refs and -spirv-debug-declare-untyped-variable
when the target vendor is AMD.
pinfo: update to 0.6.13
Packaging changes:
- upstream ownership changed hands and locations
- many updates to the build system requiring changes
Upstream changes:
0.6.13:
- Fix crash on 32-bit architectures
0.6.12:
- minor release to fix the use of defualt colors (COLOR_DEFAULT) on
ncurses installs; COLOR_DEFAULT values in pinforc were silently
ignored, causing pinfo to use black-on-balc or white-on-white
text
- remove AM_MAINTAINER_MODE from autoconf scripts to make sure all
necessary files are always rebuilt on ./configure && make
- fix possibel buffer overflow (and compiler error with gcc 8.2)
[107 lines not shown]