resterm: Update to 1.11.0
Changed: script and @apply values are sent as written
Security fixes
Response values could read local files
Response values could expand secrets
gRPC TLS settings were ignored
Scripts read the values the request sends
resterm run
Exit codes and transports
Auth, import, and record
SHA-512 in RestermScript
Docs
gcc: backend: Sprinkle -O1 to some files for alpha
With this workaround, more than 270 pkgsrc's successfully build for me.
PR toolchain/60843 GCC/alpha 14 miscompiles GCC backend
heimdal: Apply upstream fix for kill(2) argument order in kdc(8).
commit b22f33250a98efcda3a07fdc36bc2fd386230857
Author: Roland C. Dowdeswell <elric at imrryr.org>
Date: Fri Sep 25 14:45:23 2026 +0100
kdc: correct kill_kids kill(2) arg order
PR bin/60841: kdc(8) sends pids to signals instead of signals to pids
audio/fasttracker2: Update to 2.25
Changes since 2.24:
v2.25 - 02.10.2026
* Further sinc interpolation improvements
* Re-added 3-point quadratic spline interpolation (why not)
* Small tweak to the tracker scope interpolation (in
quadratic/cubic/sinc mode)
ntp(9): Avoid more left shift of negative UB.
This logic is, presumably, intended to compute integer arithmetic, so
just write it as *16 instead of <<4. If there's an advantage to
using a machine shift instruction to get the same semantics, the
compiler can do that for us.
Also avoid arithmetic overflow. If set a few lines above,
time_monitor can lie anywhere in the interval [-MAXPHASE,MAXPHASE] =
[-500e6,500e6]. Multiplying by sixteen can therefore overflow the
bounds [-2.2e9,2.2e9] of long on LP32 platforms by a factor of four.
But mtemp >= 256 here, so even if time_monitor*16 overflows the
signed 32-bit range, the result (time_monitor*16)/mtemp will not.
Hence: cast to int64_t for the intermediate computation of
time_monitor*16.
This isn't the end of the analysis: time_monitor can also be set in
hardpps(9) to something else whose bounds aren't as clear to me, but
that only applies under `options PPS_SYNC' which is usually not set.
[4 lines not shown]
shaderc: update to 2026.4
v2026.4 2026-09-11
- Use Glslang 16.6.0, SPIRV-Tools v2026.4.rc2
- Incorporate fixes for SPV_KHR_abort abortEXT(...)
- glslc:
option -fshader-stage now accepts all shader
stage names as allowed in #pragma shader_stage(<stage>)>
This includes ray tracing, task, and mesh shader
stages.
- Fixes an assert
dtrace: Avoid uninitialized stack garbage.
Found by:
PR kern/60839: use -ftrivial-auto-var-init
This applies the code change of the following FreeBSD commit, but I
didn't understand the comment so I rewrote it:
commit f222a6b88614db13ae83c8110281e690d1381a4c
Author: Bryan Drewery <bdrewery at FreeBSD.org>
Date: Fri Dec 18 09:58:03 2020 -0800
dtrace: Fix /"string" == NULL/ comparisons using an uninitialized value.
A test of this is funcs/tst.strtok.d which has this filter:
BEGIN
/(this->field = strtok(this->str, ",")) == NULL/
[27 lines not shown]
