security/gnutls: Stop fetching ktls_utils.h
It was missing from distfiles in previous versions but this has been
fixed now.
(cherry picked from commit 004617c94be181d6a4b0c57b4482d2ae682ed945)
[BOLT] Retain certain local symbols (#184074)
BOLT currently strips all STT_NOTYPE STB_LOCAL zero-sized symbols
that fall inside function bodies. Certain such symbols are named
labels (loop markers and subroutine entry points) or local function
symbols in hand-written assembly. We now keep them in local symbol
table in BOLT processed binaries for better symbolication.
[AArch64] Enabled and regenerate clmul-fixed.ll. NFC (#184628)
The v2i64 tests are now fixed. The disabled ones in clmul-scalable.ll
require i128 vectors which are generally not supported.
[VPlan] Move tail folding out of VPlanPredicator. NFC (#176143)
Currently the logic for introducing a header mask and predicating the
vector loop region is done inside introduceMasksAndLinearize.
This splits the tail folding part out into an individual VPlan transform
so that VPlanPredicator.cpp doesn't need to worry about tail folding,
which seemed to be a temporary measure according to a comment in
VPlanTransforms.h.
To perform tail folding independently, this splits the "body" of the
vector loop region between the phis in the header and the branch + iv
increment in the latch:
Before:
```
+-------------------------------------------+
|%iv = ... |
[39 lines not shown]
[CI] Enable LTO linker plugin tests (#184076)
We've recently had two instances of test failures for the LTO linker
plugin being introduced. Build and test the LTO linker plugin in
pre-merge CI to avoid this.
[SystemZ] Mark fminimumnum/fmaximumnum as legal (#184595)
In M=4 mode, the behavior matches IEEE 754-2019 minimumNumber, except
that if both operands are sNaN, the result will be sNaN rather than
qNaN. However, this is explicitly allowed for LLVM's minimumnum
intrinsic, as canonicalization can be omitted for non-constrainted FP.
As such, mark fminimumnum/fmaximumnum as legal, and lower them the same
way as fminnum/fmaxnum. In the future, we may wish to switch those to
use M=0 instead, to match IEEE 754-2008 maxNum/minNum instead.
games/openbve: update OpenBVE to version 1.12.1.0
Install more complete set of auxiliary programs and let make(1)
induce the program to wrapper script mapping rather than doing
this manually. While here, mention one comment's origin.
Reported by: portscout
[MLIR][NVVM] Unify and move to a single tcgen05_mma_kind attr for all tcgen05.mma Ops (#184433)
This change unifies using of `tcgen05_mma_kind` attribute for
tcgen05.mma Ops in MLIR.
Before this change there were two block scale attributes used for
tcgen05.mma Ops. One was `MMABlockScaleKindAttr` with `mxf8f6f4`, `mxf4`
and `fxf4nvf4` values used for `tcgen05.mma.block_scale` and
`tcgen05.mma.sp.block_scale`. Another one was `Tcgen05MMAKindAttr` with
`f16`, `tf32`, `f8f6f4` and `i8` values used for `tcgen05.mma`,
`tcgen05.mma.sp`, `tcgen05.mma.ws` and `tcgen05.mma.ws.sp`.
`Tcgen05MMAKindAttr` has been extended with values from
`MMABlockScaleKindAttr`. Now there is `tcgen05_mma_kind` attribute only
for all `tcgen05.mma` Ops in MLIR.
Backward compatibility is not supported. Existing tests and scripts
should be updated to use `tcgen05_mma_kind` attribute instead of
`block_scale_kind` for all tcgen05.mma MLIR Ops.
Fix relayd reload race crash
Instead of terminating with fatalx() when a private key hash cannot be
found, log a warning and send an error back to the relay worker.
This prevents a race condition during "reload" where a request might
reach the CA process while keys are being repopulated.
Reported by Nick Owens; thanks!
OK tb@
py-fakefs: updated to 6.1.4
6.1.4
Fixes incompatibility with VCCode unittest runner.
Fixes
* expanduser now correctly handles paths besides home and different separators
* avoid faking filesystem in VSCode unittest runner
blosc2: updated to 2.23.1
Changes from 2.23.0 to 2.23.1
* Fix some memory leaks/undefined behaviour
* Allow resizing of empty arrays
* `filters_meta` (interpreted as number of bytestreams) for the byteshuffle filter
mvc: ConfigMaintenance: when constructing class names use a safer way to strip .php extension
It's not entirely clear what is going on in the report but since the class is more or less
"empty" it looks like a path has a "." in it and the leftmost part of that path wins the
explode() although it was meant to strip the PHP extension at the end instead.
Thus make the code safer and try again with the user.
PR: https://forum.opnsense.org/index.php?topic=51102.0
py-requests-cache: updated to 1.3.1
1.3.1 (2025-03-03)
Add support for multiple response variations based on Vary
Fix overwriting headers after revalidation in read_only mode
Add tests for python 3.15 (alpha)
libavif: updated to 1.4.0
Added since 1.3.0
* Allow avifenc to read png or jpeg files through stdin using --stdin-format.
* Support some Sample Transform schemes as defined in the version 1.2 of the
AVIF specification.
* Add an optional argument to the --depth flag of avifenc used to enable a bit
depth extension scheme in the encoded file.
* Add support for converting jpeg files with Apple style gain maps.
* Add support for PNG cICP chunk when decoding PNG files. If a PNG file contains
a cICP chunk and other color information chunks, such as iCCP (ICC profile),
the other chunks are ignored as per the PNG Specification Third Edition
Section 4.3.
* Support reading Sample-Transform-based 16-bit AVIF files when
avifDecoder::imageContentToDecode & AVIF_IMAGE_CONTENT_SAMPLE_TRANSFORMS is
not zero.
* Support Sample Transform derived image items with grid input image items.
* Add --sato flag to avifdec to enable Sample Transforms support at decoding.
[49 lines not shown]
