[X86] supportedVectorShift - explicitly check vector element types instead of bitwidth bounds (#233218)
MVT has more types now, we can't just rely on the bitwidth - we need to
check the element types properly.
Fixes #233186
[TimeProfiler][Clang] Add zstd-compressed time-trace output support (#228627)
Time trace JSON files can become very large (tens of megabytes) when
profiling with fine granularity (-ftime-trace-granularity=0) or verbose
output (-ftime-trace-verbose), while compressing by ~20x with zstd.
Add support for writing zstd-compressed time-trace output directly using
LLVM's existing llvm::compression facilities:
- Introduce llvm::TimeTraceCompression ({Infer, None, Zstd}) in
TimeProfiler.h and extend llvm::timeTraceProfilerInitialize and
llvm::timeTraceProfilerWrite to infer zstd compression from .zst/.zstd
file extensions via llvm::inferTimeTraceCompressionFromPath when set to
Infer.
- Add -ftime-trace-compress=<none|zstd|infer> driver and CC1 option to
explicitly control compression or infer it from the output filename.
- Update default output filename inference when -ftime-trace is used
without an explicit filename so compressed traces use a .json.zst
extension.
Assisted-by: Antigravity with Gemini
powerpc: keep the VSX halves of the FPRs across back-to-back signals
grab_mcontext() only put the second halves of vs0-31 into the context
while the thread owned the VSX unit, but sigreturn(2) gives ownership
up so that the next use reloads the registers lazily. A signal that
arrives right after a sigreturn, like one the handler's mask was
holding back, got a context without them and its own sigreturn then
zeroed them in the PCB.
The halves saved in the PCB are current whenever the FP state is, since
VSX instructions can't run without PCB_VSX and save_fpu() stores them
in that case, so export them together with the FP registers.
Reviewed by: jhibbits
MFC after: 1 week
Differential Revision: https://reviews.freebsd.org/D60754
opentofu112: Update to 1.12.8
pkgsrc changes:
- Do not force particular Go version, build fine with Go 1.27.x now
Changes:
1.12.8
SECURITY ADVISORIES:
- Previous versions of OpenTofu could potentially experience excessive
CPU usage if connecting to an attacker-controlled HTTP2 server while
installing dependencies in tofu init. (4700)
BUG FIXES:
- Lifecycle destroy will no longer crash when given an expression with
references (4648)
1.12.7
- When using either a remote-exec or file provisioner to connect to an
attacker-controlled SSH server, the server could previously deadlock
the connection by sending certain unexpected packet types. (4551)
devel/libnjs: Update to 1.0.2
Fixes memory corruption in RegExp operations, crashes after a failed
module compilation, and excessive resource usage when sorting huge sparse
arrays.
Sponsored by: Netzkommune GmbH
lang/njs: Update to 1.0.2
Fixes memory corruption in RegExp operations, crashes after a failed
module compilation, and excessive resource usage when sorting huge sparse
arrays.
Sponsored by: Netzkommune GmbH
www/nginx-module-passenger: Add New Port
Sources of the passenger module for the NGINX ports. The module hands
requests to the Passenger agent, which runs Ruby, Python and Node
applications under nginx.
Sponsored by: Netzkommune GmbH
security/vuxml: Document multiple Erlang/OTP vulnerabilities
OTP 29.1.2, 28.5.0.8 and 27.3.4.19 fix CVE-2026-105236 and
CVE-2026-94200 in ssl, and complete the earlier incomplete fixes for
CVE-2026-42789 (public_key), CVE-2026-48856 (inets) and
CVE-2026-70405 (snmp); upstream revised all three advisories on
2026-10-14 to name these releases as the first patched ones.
CVE-2026-96596 in erl_tar gets its own entry: it affects OTP 29 only
and is fixed in 29.1.2.
lang/erlang: Fix the vsn.mk consistency checks in pre-configure
The checks grepped lib/*/vsn.mk for _EI_VSN, _TOOLS_VSN and _SNMP_VSN,
but upstream names those variables EI_VSN, TOOLS_VSN and SNMP_VSN.
The grep therefore matched nothing and each test reduced to
[ ! = <version> ], which sh evaluates as a false string comparison, so
every check passed silently no matter what the Makefile said.
The port-side variables grew their underscore prefix in 12b48a4d8ea,
which renamed them inside the grep patterns as well.
lang/erlang: Do not add WRKSRC/lib to ERL_LIBS during build
ERL_LIBS=${WRKSRC}/lib puts the half-populated in-tree lib/*/ebin
directories on the bootstrap erlc's code path, where they shadow the
bootstrap compiler. That breaks whenever a patch release changes an
API inside the compiler itself. OTP 28.5.0.8 changes
beam_ssa_type:opt_start from arity 2 to arity 3, so the freshly
written beam_ssa_opt.beam gets loaded from lib/compiler/ebin while
beam_ssa_type still comes from the bootstrap, and the build dies with
beam_ssa_recv.erl: internal error in pass beam_ssa_opt:
exception error: undefined function beam_ssa_type:opt_start/3
The ordering inside lib/compiler/src is alphabetical, so this is not a
job race and MAKE_JOBS_UNSAFE, which the error message suggests, does
not help.
The build system derives its own code paths from ERL_TOP, and
lang/erlang-runtime2[789] build the same tarballs, doc chunks
[2 lines not shown]
