[Offload][OMP] Pass native device binary to device_load OMPT callback (#232478)
According to the specification and input from tool authors, OMPT tools
expect information about native device binary while invoking the
`device_load` OMPT callback function.
lang/s7: update to 11.9.20261009
This updates improves compatibility with 32-bit platforms somewhat.
There are still some issues with numbers >=2**32, but we are getting
there.
MFH: 2026Q4
(cherry picked from commit c4a3dd9e0af4aee9dace4b2cb1d28fcbeb406ec0)
archivers/lzma: update to 26.04
- a bug fix release
Upstream changes:
- Some bugs and vulnerabilities were fixed.
MFH: 2026Q4
(cherry picked from commit 8e2bdfc3a41dc46bd25796529ad980e07df4f59d)
devel/go-tools: update to 0.52.0
Selected upstream changes:
- cmd/compilebench: exit nonzero when a benchmark fails
- x/tools: delete obsolete code and dead test
- cmd/toolstash: check -linkobj files to support early export
- go.mod: update golang.org/x dependencies
Changelog: https://github.com/golang/tools/compare/v0.50.0...v0.52.0
MFH: 2026Q4
(cherry picked from commit 04b7864de90ca2b42d27592b0bc894cbbff372b7)
Add zfs rewrite -W to skip blocks already at their current size
After a RAID-Z expansion, old blocks keep the data-to-parity ratio of
the old width until they are rewritten, and zfs rewrite is the way to
rewrite them. It rewrites every block it is given, though, including
the blocks written since the expansion, which gain nothing from it: a
rewrite that is interrupted, or run again after a later expansion,
starts over from the first block.
Add ZFS_REWRITE_SKIP_CURRENT_ASIZE, set by -W, which skips a block when
each of its DVAs already has the allocated size that metaslab
allocation would give its physical size on the same vdev, in the
transaction group of the rewrite. On a RAID-Z vdev that size depends
on the logical width of that transaction group, so a block written
before the last expansion completed is rewritten if the new width
stores it in less space. The blocks written since are skipped, and so
are the old blocks smaller than the old width, which take the same
space at the new width and stay in place. Comparing sizes rather than
widths keeps the check valid for whatever else may come to change that
[14 lines not shown]
lang/s7: update to 11.9.20261009
This updates improves compatibility with 32-bit platforms somewhat.
There are still some issues with numbers >=2**32, but we are getting
there.
MFH: 2026Q4
math/manifold: update to v3.5.4
Do not foister -std=c++17 upon pkgconfig consumers to fix the build
in the upcoming math/burr-tools update.
Changelog: https://github.com/elalish/manifold/releases
PR: 299260
Reported by: fuz
[libc++] Bump the LNT machines to the latest version of the test suite (#232895)
Since we are starting from an empty LNT v5 instance, this is a good time
to bump everything.
devel/go-tools: update to 0.52.0
Selected upstream changes:
- cmd/compilebench: exit nonzero when a benchmark fails
- x/tools: delete obsolete code and dead test
- cmd/toolstash: check -linkobj files to support early export
- go.mod: update golang.org/x dependencies
Changelog: https://github.com/golang/tools/compare/v0.50.0...v0.52.0
MFH: 2026Q4
