crypto/openssl: update generated content to match 3.5.8 release
This contains 2 new manpages as well as some minor manpage content
changes.
MFC with: 78e936b2d
crypto/openssl: update to 3.5.8
This is a security bugfix release. Please see the related merge commit
for more details.
Maintainer note: `quic_ackm.h`'s conflict was resolved by taking
the upstream version of the file verbatim.
Conflicts:
crypto/openssl/include/internal/quic_ackm.h
MFC after: 3 days
Merge commit '248da023ae5ea7292930ac5d715d88b87e2e6f46'
crypto/openssl: remove large test input file
This file was added between 3.5.7 and 3.5.8. Given that we don't yet leverage
the OpenSSL tests, there's no sense in merging this file to mainline branches..
Remove large test input file
This file was added between 3.0.21 and 3.0.22. Given that we don't yet leverage
the OpenSSL tests, there's no sense in merging this file to mainline branches.
run: don't expose us to userland until things are fully initialized.
Fixes crash seen when hot-plugging run(4) with a running wpa_supplicant.
PR kern/60665: run: hot-plugging USB wifi crashes due to use of if_attach
[mlir][gpu] Drop the explicit sm_70 from the CUDA WMMA integration tests (#219373)
Let the three TensorCore WMMA tests compile for the default chip.
CUDA 13 dropped Volta, so its `ptxas` no longer knows `sm_70`:
ptxas fatal : Value 'sm_70' is not defined for option 'gpu-name'
which fails all three tests on any machine with a current toolkit,
whatever GPU it has -- the arch is pinned in the RUN line and never
reached the hardware's own.
Nothing here needs the arch pinned. `sm_75` is already the default chip
of `gpu-lower-to-nvvm-pipeline`, of `nvvm-attach-target`, and of
`#nvvm.target`, and it is the oldest arch a current `ptxas` accepts; the
WMMA shapes these tests use are available there. Every other CUDA
integration test that doesn't need a specific arch takes that default,
so take it here too, and these tests follow the one place the minimum
supported arch is written down rather than pinning their own copy of it
[2 lines not shown]
gstripe: Increase children I/O sizes
Originally gstripe created a separate child I/O for every accessed
stripe, making it very inefficient for small stripe sizes. Later
introduced "fast" mode reduced that count for read/write requests
by copying the data to/from temporary contiguous buffers, wasting
memory bandwidth and CPU time. This commit implements alternative
method, utilizing unmapped I/O mechanism to assemble children I/Os
from pages of the original I/O, avoiding any copying. This method
though has some limitations, such as stripe size can not be smaller
than CPU page size, or buffer and offset page phases should match
(may be page aligned, but not necessarily). But those limitations
are not an issue in many cases, since ZFS, for example, can often
align its buffers (BTW, dd doesn't). Plus, unlike "fast" method,
this one can receive (and even prefers) unmapped I/Os.
While there, re-implement also BIO_DELETE. Since they don't have
any data, there is no any reason to create more than one child I/O
per disk. It also dramatically improves performance there.
[3 lines not shown]
[orc-rt] Replace Math.h in favor of bit.h. (#219390)
Replace isPowerOf2 with has_single_bit, and nextPowerOf2 with bit_width
(plus necessary arithmetic at the call sites, and a guard on the long
from sysconf in detectPageSize, which only excluded -1).
Bitmask enums must now have an unsigned underlying type (STL <bit> APIs
require it, and "bit.h" matches the STL).
snd_hdsp: Avoid allocation in the interrupt handler
Cache PCM children instead of calling device_get_children() from the
interrupt handler. Drain callbacks before child detach so cached
pointers cannot outlive the PCM softc. Allocate the parent softc by
its actual size.
This mirrors snd_hdspe's interrupt dispatch and detach lifecycle.
Reported by: christos
(cherry picked from commit 74db53d5d7657d0508940d1193f05a39df85434a)
WIP preserve move uniform cfg, BROKEN
Masks for blends originated from preserved CFG are `true` which is wrong
with the current algorithm, see blend_masks_triangle_phi in
predicator.ll
[VPlan][Predicator] Preserve some uniform control flow
Implements "Partial Control-Flow Linearization" by Simon Moll and
Sebastian Hack. Does **NOT** improve predication/masking yet, so
applicability is artificially narrowed, only some uniform branches are
preserved. In particular, the following is left for future PRs:
* Block masks still contains now-unnecessary term for the preserved
uniform branches.
* Mixed blends/phis aren't supported yet. Detecting where they would be
necessary is as complex as implementing proper support (which would
need either Luke's `reconstructSSA` or Iterated Dominance Frontier),
so we also limit it to a trivial/structured CFG where there's only
single block where those would need to be inserted.
I think even the current version might be enough to start implementing
an alternative to https://github.com/llvm/llvm-project/pull/141900 (see
BOSCC in the paper).