www/comentario: Update to 3.19.0
Refresh frontend dependencies, require Go 1.27, and update the Angular
API generator version. Select the JavaScript Sass compiler to avoid a
frontend build hang on FreeBSD.
Changelog: https://gitlab.com/comentario/comentario/-/releases/v3.19.0
p11-kit: updated to 0.26.6
0.26.6 (stable)
* rpc: added PQC support
* rpc: added support for more mechanisms
* rpc: list-objects should no longer print garbage when used via RPC
* rpc: memory management fixes and hardening
* p11-kit: import-object now rejects malformed RSA public keys
* trust: do not truncate DirectoryStrings with embeded NULL byte
* Build fixes
* Update translations
* Documentation
tcpflow: updated to 1.7.0
1.7.0
This release fixes security vulnerabilities, improves packet processing and
portability, and introduces automated releases with a signed Windows executable
and Linux Snap packages.
[X86] Fix bf16 VBROADCAST lowering and selection without AVX512BW+VLX
Broadcasts of bf16 vectors only have isel patterns with AVX512BW+VLX,
so AVX2 targets without them (e.g. znver3) fail with "Cannot select".
Add v8bf16/v16bf16 VPBROADCASTW patterns for AVX2, mirroring the f16
ones. In combineTargetShuffle, only apply the broadcast(bitcast(src))
and vbroadcast(bitcast(vbroadcast(src))) folds if the new broadcast type
is legal, since v16bf16 can be illegal when v8bf16 is legal.
Assisted-by: Antigravity
[X86] Add bf16 broadcast tests (NFC)
Add tests for bf16 vector splats that end up as X86ISD::VBROADCAST or
X86ISD::VBROADCAST_LOAD of a bf16 vector type:
- values live across basic blocks
- volatile loads
- loads whose other uses are simplified away after legalization
- broadcasts of v8bf16 values that are bitcast to vXi16/vXi32
Only the default target (SSE2) and -mattr=+avx512bw,+avx512vl are tested
for now. AVX2 targets without AVX512BW+VLX crash on all of these: they
fail to select the bf16 broadcast, or form an illegal v16bf16 broadcast
after type legalization. The follow-up fix adds RUN lines for them.
Assisted-by: Antigravity
[OpenMP][clang][flang] Compare tied context selectors with each other (#233905)
When several context selectors tie for the highest score, a selector
that is a strict subset of another tied selector loses, and otherwise
the first one wins. getBestVariantMatchForContext only compared each
candidate with the current best, which isn't enough because that
comparison isn't transitive:
```
#pragma omp metadirective \
when(user={condition(1)}, \
implementation={vendor(score(4): llvm)}: taskyield) \
when(device={kind(cpu)}, \
implementation={vendor(score(3): llvm)}: taskwait) \
when(user={condition(1)}, device={kind(host)}, \
implementation={vendor(score(3): llvm)}: barrier)
```
All three score 5 on the host. The first is a strict subset of the
[18 lines not shown]
system: fix automation user scope set since validation was tightened; closes #11192
While here remove the defunct -o option since it is broken and would
not make any sense anyway with the current validations in place.
Also make the script a bit prettier in use from the command line.
OpenMP: Stop using TTI to pick the partial unroll factor in OMPIRBuilder (#240030)
When the unrolled loop's CanonicalLoopInfo is needed by an enclosing
loop directive and no factor was given, unrollLoopPartial computed one
by constructing its own TargetMachine with default TargetOptions and a
standalone FunctionAnalysisManager, then running LoopUnrollPass's cost
model on the function while it was still being built.
This is a layering violation. Frontends should not be using codegen
optimization information to construct the original program. This will
not have a properly configured TargetTransformInfo from a pass
manager. The cost model is also not meaningful on incomplete,
unoptimized IR.
Use a factor of 2, matching what Sema's OpenMP loop transformation
uses for a partial clause without a factor. This removes the hidden
-openmp-ir-builder-unroll-threshold-factor option.
Co-authored-by: Claude Opus 5.5 <noreply at anthropic.com>
uart: Set the bus space tag before parsing hw.uart.console
uart_cpu_getdev() lets hw.uart.console override the FDT, but
uart_getenv() maps an "mm:" address with uart_bus_space_mem, which is
only assigned after the FDT probe. On riscv and arm it is still NULL
at that point, so bus_space_map() faults before there is a console.
On riscv this happens on any EFI boot where the firmware provides an
SPCR table, since the loader turns it into hw.uart.console.
Initialize uart_bus_space_mem to fdtbus_bs_tag, as uart_cpu_arm64.c
does with &memmap_bus (See also 0624eddcffefe).
PR: 299089
Reviewed by: mhorne
MFC after: 1 week
Signed-off-by: Rick Richard <rick at sloservers.com>
(cherry picked from commit 9db8ae83e62e9a1391674a14b0b7d76de2e3c3f7)
uart: Set the bus space tag before parsing hw.uart.console
uart_cpu_getdev() lets hw.uart.console override the FDT, but
uart_getenv() maps an "mm:" address with uart_bus_space_mem, which is
only assigned after the FDT probe. On riscv and arm it is still NULL
at that point, so bus_space_map() faults before there is a console.
On riscv this happens on any EFI boot where the firmware provides an
SPCR table, since the loader turns it into hw.uart.console.
Initialize uart_bus_space_mem to fdtbus_bs_tag, as uart_cpu_arm64.c
does with &memmap_bus (See also 0624eddcffefe).
PR: 299089
Reviewed by: mhorne
MFC after: 1 week
Signed-off-by: Rick Richard <rick at sloservers.com>
(cherry picked from commit 9db8ae83e62e9a1391674a14b0b7d76de2e3c3f7)
hwpmc: refuse MOD_UNLOAD while PMC owners exist
Unloading hwpmc while processes own PMCs frees state they still use.
Return EBUSY instead. Use a try-lock on pmc_sx, since MOD_UNLOAD runs
with kld_sx held. MOD_SHUTDOWN still always cleans up.
Reviewed by: mhorne
MFC after: 1 week
Sponsored by: Advanced Micro Devices, Inc.
Differential Revision: https://reviews.freebsd.org/D60561
