Import tmux-3.6b (previous was tmux3.6a)
CHANGES FROM 3.6a TO 3.6b
* Remove images from the correct list when they are removed while in the
alternate screen (reported by xlabai at tencent dot com).
PR/59452: Marcin Gondek: Add a new mount flag "nowccmsg" to suppress printing
wcc-related messages. Apparently some synology server is causing them. This
just suppresses the messages, but does not change the behavior of the client.
PR bin/58609 - enable locale var internal manipulation
sh now recognises the (standard) set of locale variables, and in addition
to setting up the locale environment to match those in the environment at
startup (which it has done for ages), now also causes alterations to those
variables while the shell is running to take immediate effect inside sh,
which can affect how the shell operates in some limited aspects - previously
such updates would be passed to exec'd child processes (not subshells)
if the variables are exported, and not affect the running shell at all.
See the PR, and the updated sh(1) man page, for details.
This is a feature enhancement, no pullups (not even to -11) are planned.
eqos: Various performance improvements.
- Use BUS_DMA_COHERENT for ring descriptors, allowing us to remove
the descriptor padding (which increased memory usage and bandwidth).
Be very careful to avoid unnecessary reads and writes of uncached
memory!
- Defer TX/RX to a workqueue. This is mostly to help the scheduler, which
doesn't seem to understand that a CPU busy processing interrupts is
maybe not the best place to run a process on an otherwise idle system.
Be consistent with "built in" vs "built-in"
Use the hyphenated version only when describing, or referring to, one (or
more, incl the general set of) actual built-in commands (like just there)
in sh.
Use the 2 word version in all other contexts, including when describing
functionality (like line editing) that is built in to sh (like just there)
except normally there one would write "built into" if not making the point!
x86: use 0x40000010 cpuid leaf only on vmware and kvm
specifically, do not use it on nvmm.
these hypervisor cpuid leafs are basically hypervisor-specific.
(there was a proposal on commonizing these hypervisor leafs. [1]
but it doesn't seem agreed on.)
this cpuid leaf 0x40000010 was originally from vmware. although it
seems more common to use the GETHZ (45) hypercall instead these days.
kvm seems to implement it as well. (via qemu vmware-cpuid-freq)
i personally haven't tested this on either vmware or kvm.
for nvmm (netbsd), the leaf has been implemented in 2025. [2]
and then the lapic bit has been disabled in 2026. [3] that is,
we had no releases with it enabled. even if you are running the
-current version of nvmm, it's better to avoid using this leaf
[5 lines not shown]
nvmm: remove cpuid leaf 0x40000010
* given the lapic bit disabled, (PR/59424) [1]
this leaf doesn't seem to have much benefit anymore.
as nvmm is used in other platforms, (dragonfly bsd)
it's better to avoid guest ABI changes without clear benefits.
* I couldn't find any documenation about what RBX=0 means.
(vmware or kvm)
we can revisit this when/if someone comes up with a better
implementation. (probably userland-assisted one)
discussed on source-changes-d. [2]
reviewed by Taylor R Campbell.
[1] https://mail-index.netbsd.org/source-changes/2026/05/01/msg161786.html
[2] https://mail-index.netbsd.org/source-changes-d/2026/05/01/msg014654.html
libepoxy: Make EGL libs depend on EGL support rather than GLAMOR.
Build tested on sparc64, which has EGL but no GLAMOR x server.
If this is pulled up, it should happen before 11.0 is cut, since
it adds stuff to the ABI.
PR pkg/60295 x11/gtk3 does not build on NetBSD/macppc
