news/inn{-current}: Update current and handle blocklistd rename
Update inn-current snapshot from 20260121 to 20260419. Rename the
BLACKLISTD option to BLOCKLISTD to match the upstream and FreeBSD 15+
rename. Add version-conditional logic to fall back to the old blacklist
API names on FreeBSD < 15.0 for the 2.8 branch.
Co-Authored-By: Jose Luis Duran <jlduran at FreeBSD.org>
graphics/epsonscan2: Fix build error on 16-current: "if (a <= b <= c)"
Fix compilation error for "if (a <= b <= c)".
While here:
- Replace PORTVERSION with DISTVERSION.
- Move dependency from boost to BUILD_DEPENDS - the port is not linked
with boost libs, but uses includes during build.
- Remove unnecessary "CFLAGS+=".
PR: 294951
Sponsored by: UNIS Labs
Co-authored-by: Vladimir Druzenko <vvd at FreeBSD.org>
MFH: 2026Q2
(cherry picked from commit 5337e3e6d81efbb96a153b7ae7ee9db7bfadffb3)
graphics/epsonscan2: Fix build error on 16-current: "if (a <= b <= c)"
Fix compilation error for "if (a <= b <= c)".
While here:
- Replace PORTVERSION with DISTVERSION.
- Move dependency from boost to BUILD_DEPENDS - the port is not linked
with boost libs, but uses includes during build.
- Remove unnecessary "CFLAGS+=".
PR: 294951
Sponsored by: UNIS Labs
Co-authored-by: Vladimir Druzenko <vvd at FreeBSD.org>
MFH: 2026Q2
[DebugInfo] Fix crash in declare-to-assign when memcpy writes to scalable-vector alloca (#194107)
## Problem
`declare-to-assign` (`AssignmentTrackingPass`) crashes with a fatal error when a fixed-size `memcpy` writes into a scalable-vector alloca (e.g. an RVV `vint32m1_t`):
Cannot implicitly convert a scalable size to a fixed-width size in TypeSize::operator ScalarTy()
**PS**: The compiler explorer always implicitly adds the '-g' option, when adding the '-g0', the crash will disappear: https://riscvc.godbolt.org/z/dEqhc4EoE
**Reproducer** (clang `-target riscv64-unknown-linux-gnu -march=rv64gcv -O1 -g`):
```c
#include <string.h>
#include <riscv_vector.h>
vint32m1_t get_i32x4(int* v) {
vint32m1_t r;
memcpy(&r, v, 16);
return r;
}
[13 lines not shown]
[llubi] Fix inconsistent intrinsic argument retrieval (#195499)
This PR fixes inconsistent intrinsic argument retrieval by making all
intrinsics fetch their arguments from `Args`. This change is a
prerequisite for handling parameter attributes in `enterCall`.
blocklistd: Fix RFC1918 typo
The address in the configuration file example was intended to be from
the 192.168.0.0/16 range of IPv4 private addresses (RFC1918).
Reported on mastodon.social at
https://mastodon.social/@asmodai/116316630762241486.
Fix submitted upstream by emaste@. Fixing locally first.
Reviewed by: emaste
MFC after: 1 week
Differential Revision: https://reviews.freebsd.org/D56773
p5-Module-Signature: update to 0.96.
0.96 -- Mon Apr 27 11:27:02 ADT 2026
* Fix issue from last release where search keys is interactive
0.95 -- Sun Apr 26 11:44:20 ADT 2026
* Announce deprecation of the module
* Update change log (forgotten in 0.94)
0.94 -- Sun Apr 26 11:37:00 ADT 2026
* Announce deprecation of the module
devel/libvirt: update to 12.3.0
- Update to 12.3.0
- Patch out installation of the unnecessary systemd service file
Sponsored by: The FreeBSD Foundation
workflows/release-binaries: Remove extra depencies for Arm64 Windows (#195222)
The python modules these were needed for were removed in
cdc41818e3bd9e8cb7788d59365e39fe6433159e.
[LifetimeSafety] Detect iterator invalidation through container aliases (#195231)
The previous heuristic in `handleInvalidatingCall` is too conservative.
The ideal way would be completely removing this, but it would introduce
~10 regressions in the existing testcases.
This commit replace the filter with a narrower guard that only skips
direct field accesses (AccessPath currently lacks field granularity and
cannot distinguish `s.v1` from `s.v2`).
Closes https://github.com/llvm/llvm-project/issues/193044
[RFC][IR] Support vector splats in `ConstantPointerNull`
This PR allows `ConstantPointerNull` to represent both scalar pointer nulls and
fixed or scalable vector splats of pointer nulls. This change first aligns with
the native splat behavior of `ConstantInt` and `ConstantFP`, and second, makes
it easier to eventually change the semantics of `ConstantPointerNull` to
represent a semantic null pointer instead of a zero value, which is what it
represents today.
