debug/shl.mi: Cull obsolete linkable shlibs and explain why.
This is not a _good_ system but it's the system we have:
PR misc/57581: set lists should have a way to obsolete shlibs in
DESTDIR but not in postinstall
Fix cir vec cmp fold (#202502)
Fixes #202431
This PR fixes two bugs in `VecCmpOp::fold` that caused incorrect
constant folding of vector comparisons.
1. Wrong result value: True comparison results were folded to 1, but the
SIMD convention and `VecCmpOp`'s own documentation require 0 (false) or
-1 / all-ones (true). For example, a `ne` comparison where all elements
differ should produce [`-1, -1, -1, -1]`, not `[1, 1, 1, 1]`.
2. Unsigned comparisons treated as signed: Ordered comparisons `(lt, le,
gt, ge)` always used `getSInt()`, treating unsigned element types as
signed. This produced wrong results for values whose high bit is set,
e.g., for `u8`, the value 255 was interpreted as -1, so 0 > 255
(unsigned: false) was incorrectly folded to true.
Fix: Dispatch to `getUInt()` or `getSInt()` based on the input element
[2 lines not shown]
[flang][cuda] Exclude non-variable actuals from unified-memory CUDA data attribute relaxation (#206121)
Under -gpu=mem:unified, the CUDA data attribute compatibility check
(AreCompatibleCUDADataAttrs) allows an unattributed actual argument to
bind to a Device/Managed/Unified dummy. This relaxation is correct for
variables whose storage is accessible from device code under unified
memory, but not for non-variable expression results (e.g. intrinsic call
results like RESHAPE(...)), which are host temporaries.
Without this fix, a generic SUM call like sum(reshape(hostArray, ...),
dim=2) could resolve to a device-specific overload instead of the
intrinsic, because the RESHAPE result was incorrectly considered
compatible with a DEVICE-attributed dummy.
This patch:
- Adds an actualIsVariable parameter to AreCompatibleCUDADataAttrs
(defaulting to true for backward compatibility) and gates the
unified-memory relaxation for Device/Managed/Unified dummies on it.
[3 lines not shown]
[docs] Register MLIR lexer for Sphinx docs
Register the in-tree MLIR Pygments lexer from the shared llvm_sphinx configuration so all llvm-project Sphinx builds can highlight fenced mlir blocks.
Also teach the MLIR lexer to consume top-level whitespace. Without this, Sphinx reports a lexer warning after the lexer is registered, and docs-clang-html fails because Sphinx warnings are treated as errors.
This makes docs-clang-html build with CLANG_ENABLE_CIR=ON.
t_mbrtowc: Mark UTF-8 test cases xfail.
mbrtowc previously failed to reject invalid (legacy 5/6-byte) UTF-8,
so it accepted this test case. Now it rejects this test case,
because the test case itself is broken.
Need to split this test up into:
1. correctly decoding the valid inputs
2. correctly rejecting the invalid inputs
But for now marking the test case xfail is an adequate approximation
to the more complicated truth.
PR lib/60369: mbrtowc, mbrlen have wrong return value for some
invalid byte sequences: Invalid sequence
x11/wayst: Update g20250601 => g20260608
Commit log:
- Fix at least 2 buffer overflows.
https://github.com/91861/wayst/compare/f5a6c22...51a1c97
- Add a .desktop file ripped from the build files of the port.
- Add an example configuration file.
- Move the BROKEN entry below the LICENSE entry in accordance with
`portfmt`.
PR: 296298
Sponsored by: UNIS Labs
Co-authored-by: Vladimir Druzenko <vvd at FreeBSD.org>
MFH: 2026Q2
(cherry picked from commit f7edd01eceb19e14ac993e766884969d4011bc90)
x11/wayst: Update g20250601 => g20260608
Commit log:
- Fix at least 2 buffer overflows.
https://github.com/91861/wayst/compare/f5a6c22...51a1c97
- Add a .desktop file ripped from the build files of the port.
- Add an example configuration file.
- Move the BROKEN entry below the LICENSE entry in accordance with
`portfmt`.
PR: 296298
Sponsored by: UNIS Labs
Co-authored-by: Vladimir Druzenko <vvd at FreeBSD.org>
MFH: 2026Q2
[clang][docs] Register MLIR lexer for CIR docs
Register the in-tree MLIR Pygments lexer with Clang Sphinx docs so generated CIR dialect documentation can highlight fenced mlir blocks.
Also teach the MLIR lexer to consume top-level whitespace. Without this, Sphinx reports a lexer warning after the lexer is registered, and docs-clang-html fails because Sphinx warnings are treated as errors.
This makes docs-clang-html build with CLANG_ENABLE_CIR=ON.