devel/llvm19: fix build on 15.1, 14.4
This patch only works on systems with the libc++ from LLVM 21 so bound
its application appropriatly.
PR: 299993, 296203
Fixes: 6a0f728d9cd8 ("devel/llvm19: fix build with flang and libc++ 21")
[flang] Avoid a quadratic walk in FIR LICM's nested-region hoisting (#236138)
With `hoist-from-nested-regions=aggressive`, `flang-licm` considers
every operation in a loop's nested regions as a candidate, and for each
candidate `canMoveOutOfOp` is called once per intermediate ancestor up
to the loop. `canMoveOutOfOp` walks the candidate's whole subtree and
calls `fir::canMoveOutOf` on each nested operation. So an
`scf.if`/`fir.if` that holds a large part of the loop body is walked
again for every enclosing level and again for every `if` nested in it.
On routines with deeply nested IF blocks inside loops this takes minutes
of compile time.
`fir::canMoveOutOf` consults only the region owner's
`OperationMoveOpInterface` and returns true when the owner does not
implement it, so in that case the result of the walk is known in
advance. This patch returns early instead of walking. The pass result
does not change.
The new test checks that hoisting through operations without the
[3 lines not shown]
www/p5-Dancer2: update 2.2.2 -> 2.3.0
Changelog: https://metacpan.org/dist/Dancer2/changes
Major changes:
- PR #1866: JSON serializer should not leak file/line detail
- GH #1794: Add support for HTTP QUERY method.
- GH #1863: Fix the JSON serializer modifying the data it is given.
Security: PR #1866: JSON serializer should not leak file/line detail
graphics/p5-GD: update 2.83 -> 2.91
Changelog: https://metacpan.org/dist/GD/changes
Port changes:
- Use CPAN:RURBAN macro, latest releasees are not available in the by-module path
- Remove patch which looks useless
Security: CVE-2026-11526
System: Routes: Configuration - bold StaticRoute class into legacy code and plugins for https://github.com/opnsense/core/issues/10569 (#11104)
As a first step, it's easiest to refactor system_routing_configure() to use our new class and leave the callers alone.
We should likely double check the callers at some point too, but impact is easier to assess when the number of changes is slightly more limited.
With this change in place, you could now configure mulitple paths for the same destination.
[AArch64] Fix non-strict scalar bf16/fp128 conversions (#234868)
Fix crashes when lowering non-strict scalar conversions between bf16
and fp128. Both directions now go through fp32. The fp128-to-bf16 path
uses the existing round-to-odd helper before the final bf16 conversion.
Add codegen tests for both directions, covering scalar returns and
loads/stores with and without bf16 support.
Fixes #172400.
