[TableGen] Fix TypeSetByHwMode::getValueTypeByHwMode. (#174182)
This should convert the type set for each HwMode to an MVT for that
HwMode. Instead, if a single type existed for the DefaultMode, that was
used for the MVT of every other mode.
This didn't cause an issue because there is only one place this function
is used before HwModes are expanded. That's just verifying that
constants are small enough for the MVT for each mode. So you would need
a large constant and a HwMode with a smaller VT than the default mode.
NAS-139152 / 26.04 / Fix minor bug in our IoThreadPoolExecutor (#17944)
Beginning in python3.13, upstream ThreadPoolExecutor fixed their
calulcation for `max_workers` (threads). We implemented our own
calculation which did, virtually, the same thing however ours was off by
1 depending on number of CPUs on a system.
Instead of diverging from upstream, just use their calculation to follow
upstream as close as possible.
As an aside, I removed the global `counter` variable and instead
followed similar paradigm that upstream is doing as well.
You can look at upstream
[here](https://github.com/python/cpython/blob/afa24d832494e2d04969f9ad6585b61700c50d6c/Lib/concurrent/futures/thread.py#L122)
editors/featherpad: update to 1.6.3
V1.6.3
---------
* Check for nullity before calling `deleteLater()` — they say that's needed with Clang's optimizations enabled.
* Fixed an asymmetry between the forward and backward searches/replacements if some text was selected.
* Made replacing after searching easier (without needing to clear the selection first).
* Fixed showing of ampersand in the recent files menus.
* Fixed highlighting of C++ numbers with single quote as separator.
* Added more explanation on searching and replacing to Help.
NAS-139142 / 26.04 / remove python3-systemd dependency (#17936)
This removes the only other 2 users of systemd.journal module. The
`Reader` class is 13MB of memory allocations alone. This replaces it
with just fork+exec'ing to `journalctl`. The memory efficiency tradeoff
outweighs the consistent inefficiencies in memory allocations.
Furthermore, I've created a unified helper function so that both callers
can call it.
Because of this, I'm able to remove another unnecessary 3rd party
dependency.
devel/cargo-nextest: update to 0.9.117
Added
- Experimental support for running benchmarks via cargo nextest bench. Set NEXTEST_EXPERIMENTAL_BENCHMARKS=1 to enable.
- Benchmarks have a separate configuration namespace with dedicated slow-timeout and global-timeout settings:
[bench]
slow-timeout = { period = "120s", terminate-after = 2 }
global-timeout = "1h"
- Per-test overrides are also supported within the [bench] section.
- The list command now supports --message-format oneline for grep-friendly output.
- Nextest now accepts --target host-tuple to explicitly target the host platform, mirroring Cargo's new feature. This resolves to the detected host triple at runtime. (#2872)
Changed
- The default output style for cargo nextest list has been changed to a new auto value, which is equivalent to human (the previous default) if standard output is an interactive terminal, and oneline if not.
[4 lines not shown]
sound: Improve snd_midi->{in,out}q allocation
Currently we lock and allocate the buffers with M_NOWAIT, without
checking if the return value of malloc(). This is not necessary as
subsequent check below will eventually check that. However, for
correctness, allocate the buffers with M_WAITOK (there is no reason not
to) and lock afterwards.
Sponsored by: The FreeBSD Foundation
MFC after: 1 week
Reviewed by: markj
Differential Revision: https://reviews.freebsd.org/D54131
sound: Retire mpu_callbackp()
It is the exact same as mpu_callback().
No functional changed intended.
Sponsored by: The FreeBSD Foundation
MFC after: 1 week
sound: Take device type into account in sndstat
sndstat will be extended to work with MIDI devices as well, so separate
functionality based on the device type.
Sponsored by: The FreeBSD Foundation
MFC after: 1 week
Reviewed by: markj
Differential Revision: https://reviews.freebsd.org/D54141
sound: Do not check for NULL before free()
No functional change intended.
Sponsored by: The FreeBSD Foundation
MFC after: 1 week
Reviewed by: markj
Differential Revision: https://reviews.freebsd.org/D54174
sound: Move sndstat out of pcm/
Needed by follow-up patches that will add sndstat support for midi/
Sponsored by: The FreeBSD Foundation
MFC after: 1 week
Reviewed by: markj
Differential Revision: https://reviews.freebsd.org/D54140
sound: Merge midi_destroy() with midi_uninit()
Also always call MPU_UNINIT(). It does not make sense not to if we are
deallocating everything.
Sponsored by: The FreeBSD Foundation
MFC after: 1 week
Reviewed by: markj
Differential Revision: https://reviews.freebsd.org/D54192
sound: Retire snd_midi->qlock
snd_midi->qlock is used to protect snd_midi->{in,out}q. However, apart
from the numerous LORs present already in the code, there is no reason
not to use snd_midi->lock, as we do for the rest of the structure
Started by: https://github.com/freebsd/freebsd-src/pull/1902
Sponsored by: The FreeBSD Foundation
MFC after: 1 week
Reviewed by: dev_nicolas-provost.fr
Differential Revision: https://reviews.freebsd.org/D54129
snd_dummy: Initial MIDI support
Because testing the midi/ code of sound(4) requires a physical MIDI
device, add some basic MIDI support to snd_dummy(4) so that we can test
patches to midi/ easier.
Sponsored by: The FreeBSD Foundation
MFC after: 1 week
Differential Revision: https://reviews.freebsd.org/D54127
sound: Retire midi_devs and mstat_lock
Nowadays midi_devs only has two uses:
1. To verify in midi_init() if a given device unit exists, as well as to
calculate the next device unit. Instead, make sure we always get a
unique unit and channel number using unr(9).
2. To keep track of all midi devices, so that it can destroy them all at
once in midi_sysuninit(). However, since we stopped building midi as
a kernel module, there is no reason to do that, simply let the
drivers tear down the devices themselves.
Also retire mstat_lock since it's only used to protect midi_devs.
PR: 261071
Sponsored by: The FreeBSD Foundation
MFC after: 1 week
Differential Revision: https://reviews.freebsd.org/D54126
sound: Stop building midi as a module
There is no reason for this. The midi functions are used by drivers
on-demand anyway. Use SYSINIT(9) instead to do the appropriate
(de-)initilizations.
Sponsored by: The FreeBSD Foundation
MFC after: 1 week
Reviewed by: markj
Differential Revision: https://reviews.freebsd.org/D54125