java/apache-commons-lang: set expiration date
Expire together with its only consumer in the ports tree editors/openoffice-4.
This port was already deprecated. Superseded by port java/apache-commons-lang3.
Approved by: no maintainer
devel/p5-Cache-FastMmap: update 1.62 -> 1.63
Changelog: https://metacpan.org/dist/Cache-FastMmap/changes
Add a patch to unbreak the tests under FreeBSD
(use "fstats -p PID" to count file descriptors instead of counting /proc/PID/fd)
[mlir][SCF] Skip dynamic peeling for non-index loops (#217909)
`scf-for-loop-peeling` constructs an `affine.apply` on its dynamic path
to compute the split bound. However, `affine.apply` requires `index`
operands, while `scf.for` also permits signless integer induction
variables and bounds.
Skip the dynamic peeling path when the loop induction variable is not
`index`. The existing constant-bounds path remains unchanged, so
constant integer loops can still be peeled.
Add a regression test for a loop with dynamic `i32` bounds, verifying
that the pass leaves it unchanged rather than producing invalid IR.
Fixes #216631.
Co-authored-by: Purnima Shrivastava <purnimashrivastava05@.com>
[mlir][scf] Do not read non-constant loop bounds when unrolling (#217392)
`loopUnrollByFactor` asserts `expected constant loop bound`
(`SCF/Utils/Utils.cpp`) when the loop bounds are not constant.
`getStaticTripCount` takes the constant path whenever
`constantTripCount` answers, but `constantTripCount` answers on three
shapes where the bounds themselves are **not** constant:
- `lb == ub` (same `Value`), giving 0 iterations,
- `lb == 0` and `ub == step`, giving 1 iteration,
- `ub` a constant offset from a non-constant `lb`, via
`computeUbMinusLb` under `nsw`.
In all three the code then reads the bounds as constants and asserts.
The fix takes the constant path only when `lb`, `ub` and `step` are all
constant, and otherwise falls through to the dynamic path that already
handles them. The other two callers of `getStaticTripCount` in that file
use only the count, never the bounds, so the defect is confined to this
[4 lines not shown]
[CIR] Emit lifetime markers for automatic variables (#206695)
### summary
This is a follow up of : #199599
Per the consensus from the PR #199599, this implements lifetime-marker
emission in ClangIR that closely follows classic CodeGen.
Emit lifetime markers (cir.lifetime.start/end) for automatic variables
in ClangIR.
- Gated by shouldEmitLifetimeMarkers (optimized builds or
ASan-use-after-scope/
HWASan/MSan/MemtagStack), like classic CodeGen.
- start at the decl; end as a NormalEHLifetimeMarker cleanup (after the
destructor);
both target the underlying alloca. Wired through the EH stack so they
don't force
[6 lines not shown]
libical4: update to 4.0.5.
## [4.0.5] - 2026-08-15
- Fix 32-bit time_t upper bound off by two days.
- Buildsystem: fix libical_deprecated_option() writing the wrong cache value.
- Bogus TZIDs no longer cause an error.
- DTEND, DURATION, DUE property types and values are now validated per
RFC 5545 Sections 3.8.2.2 - 3.8.2.5.
- Built-in timezones updated to tzdata2026c.
## [4.0.4] - 2026-07-25
- Fix an uninitialized memory issue reading zoneinfo geo coordinates.
## [4.0.3] - 2026-06-14
- Built-in timezones updated to tzdata2026b.
- Fixes line folding where a line fold could mix with a line ending.
[7 lines not shown]
make: fix newline in word splitting
The newline character behaved differently depending on whether it
occurred at the beginning of a word or in the middle of it. In the
middle, it didn't act as a word separator but instead stopped splitting,
thereby ignoring any following words. This behavior was neither
documented nor to be expected. It probably came from a time before 1993
where the makefiles were read as a single block of text instead of
splitting them into lines first.