BSD Commit Log Search

   Follow llvm / clang and disable -fomit-frame-pointer optimisation by
   default.

   OK kettenis@

   Disable the -fomit-frame-pointer optimisation by default.

   The frame-pointer is needed to have good backtraces from e.g ddb or
   ptrace / btrace. Many other distros did something like this as well since
   the benfit of havving easy to work with backtraces outweights the little
   overall speedup gained by having an extra register.

   Also disable -mno-omit-leaf-frame-pointer by default on llvm.

   OK kettenis@

   X509_STORE_CTX_get_error.3: zap extraneous if

   X509_STORE_CTX_get_error: validate chain -> validated chain (of certificates)

   devel/nspr: update to 4.40.

   clang codestyle applied upstream, much churn in patches but NFC.

   geo/qgis: update to 4.2.2

   libssl: ensure server selected ALPN was advertised

   Per RFC 7301, section 3.2, "In the event that the server supports no
   protocols that the client advertises, then the server SHALL respond
   with a fatal "no_application_protocol" alert.

   If a server does not do that and chooses a protocol that we have not
   advertised, we should abort the handshake. The RFC does not specify
   an alert for this case. BoringSSL chose illegal_parameter and OpenSSL
   decode_error. I slightly prefer illegal_parameter, so went with that.

   Reported by Acts1631 with a similar diff.

   ok jsing kenjiro

   tlsext: check we reject unadvertised selected protocol

   This test currently fails and will be fixed in ssl_tlsect.c r1.168

   Purge expected failures on amd64 after recent libm changes.

   tlsext_alpn_client_process(): rename list and proto

   Use server_list and selected instead of list and proto to reduce noise
   in the next commit.

   ok jsing kenjiro

   update to crush 0.89.0

   devel/sbt: update to 2.0.8

   Use isnan() to detect NaNs.  Fixes a bug exposed by the sortix testsuite
   where we wouldn't detect a NaN.

   ok millert@, daniel@

   devel/codex: update to 0.150.1

   Also fixed build with rust-1.98.0 that was reported by naddy@

   update 20260512 -> 20260720

   update 20260411 -> 20260731

   update 20260418 -> 20260519

   update 20260411 -> 20260730

   update 20240501 -> 20260703

   add missing patch

   update 20260208 -> 20260823

   update 20240503 -> 20260713

   remove libfsntfs

   unhook libfsntfs

   hook up libyal

   update 20251028 -> 20260727
   and while there, opportunistically move from sysutils/libfsntfs into 
   sysutils/libyal

   audio/mpd: update to 0.24.15.

   see https://raw.githubusercontent.com/MusicPlayerDaemon/MPD/v0.24.15/NEWS

   www/librewolf: update to 154.0.1-3, from yaydn

   adds riscv64 patch from jca@

   Make sure to build kernel files with -fno-pie; this had been forgotten while
   switching the m88k toolchain to PIE by default, and I am quite impressed
   kernels built with PIE objects run without problems.

   Remove replaying of the 88100 data pipeline in sigreturn().

   This had been added during the r1.18->r1.22 changes to let the testcases from
   the devel/libsigsegv run.

   Contrary to what I wrote then, the pipeline gets replayed when returning to
   userland to invoke the signal handler, so there is no need to do this once more
   in sigreturn.

   The real fix needed for these testcases to run reliably, was to make sure that
   the address used to spill the sigcontext on the process stack would not get
   modified while running data_access_emulation(); this logic was eventually
   fixed in r1.21, and nothing more is needed.

   Thanks to Andrew Griffiths for pointing to my attention that the data fed to
   sigreturn() was partially user-controllable, and that carefully crafted
   signal handlers could use this behaviour as unprivileged kernel memory read
   and write operations.