What Happened
Kernel specialization for variable HC: A metal backend change allows dsv4_hc_pre kernels to accept arbitrary hc values (previously hardcoded to 4). The patch passes n_hc as a function constant, generates per-n_hc pipeline variants and adds tests for many hc values — fixing a fallback-to-CPU failure for models that vary hc by…
What Happened
Over the last development cycle the open-source inference ecosystem delivered two parallel waves of work: (1) broad, low-level backend and kernel hardening in the llama.cpp/ggml ecosystem that expands supported accelerators and fixes stability/performance bugs, and (2) a major inference/runtime release that adds schedulers, memory/residency improvements, new models and language/runtime tooling for high‑throughput production…
What Happened
Over the last set of commits to ggml / llama.cpp the community shipped multiple engineering changes that materially affect inference performance, portability and robustness for open‑weight models. Key changes include:
New binary matmul kernels (including A8 Q6_K non‑MoE and IQ3_S MMQ kernels) and layout fixes that broaden high‑performance kernel coverage across…
What Happened
Community maintainers of ggml/llama.cpp shipped a dense set of fixes and platform expansions focused on robustness, backend coverage and model-format correctness. Changes include:
Expanded CI/build matrix and attestations for multi‑platform binary builds (macOS/iOS, Linux x64/arm64/s390x, Android, Windows, openEuler) and many GPU/backends (Vulkan, CUDA 12/13, ROCm 10.0, OpenVINO, SYCL, OpenCL) [1][2][4][6].
…
What Happened
The llama.cpp community pushed multiple engineering and model-conversion changes that affect production inference stacks: kernel and backend improvements, new quant formats and Hexagon support, a novel causal-only HRM model conversion, GPU/CUDA optimizations, and a high‑severity RPC use‑after‑free fix.
Fixed fused QKV split-state for gemma4 and added fused full-attention handling for Qwen35…
What Happened
Over the last development cycle the ggml/llama.cpp ecosystem received a series of coordinated engineering changes that materially affect running open weights and community inference tooling:
MoE, OpenCL and GEMM fixes: OpenCL changes select MoE expert matmuls by batch size, gate the prebuilt q4_0 MoE GEMM on routing count, and stop writing…
What Happened
The llama.cpp project published a major v0.4.1 milestone and associated commits that together expand model support, backend coverage, server reliability and observability while hardening correctness across CPU/GPU/accelerator backends.
New models & formats: adds Maple 20B‑A1B (ternary MoE, CPU) and a Tencent Hy 4 preview; conversion and format flags (e.g., --fuse-qkv) to…
What Happened
Over the last set of upstream changes, the ggml/llama.cpp ecosystem pushed multiple engineering fixes and tooling improvements that matter for production inference deployments. Key items:
Expanded and hardened multi‑platform CI/build matrix (macOS/iOS, Linux x64/arm64/s390x, Android arm64, Windows, and openEuler variants) with many GPU/backends covered (CUDA 12/13, Vulkan, ROCm 10.0, OpenVINO, SYCL…
What Happened
Over the last set of upstream changes the llama.cpp / ggml ecosystem has focused on making local inference robust across a very wide hardware matrix and on smoothing operational edges for model downloads and runtime kernels. The notable engineering changes include:
UI and caching improvements to host/download workflows and fixes to…
What Happened
Over the last development cycle the open-source inference ecosystem saw concentrated improvements across low‑level kernels, cross‑platform builds, and serving primitives that materially affect production deployments:
llama.cpp/ggml received a substantial fusion refactor and protection modes to unify fusion logic, add per‑fusion diagnostics and a regression baseline, and fix a fusion bug that…
What Happened
A concentrated set of changes and fixes landed in ggml/llama.cpp that improve GPU paths, broaden platform support, harden multimodal handling, and tighten tests. The key technical items:
Enabled a Vulkan-side allocation dependency to allow topk_moe fusion during prefill (improves fused kernels for MoE/top‑k workloads) [1].
Vulkan small-M matrix optimizations…
What Happened
Two parallel flows of community activity have meaningfully expanded the open-source inference stack in ways production teams can use today:
vLLM v0.29.0 made Model Runner V2 the default and added a set of new model weights and performance features focused on large‑scale serving and memory efficiency. Notable new checkpoints include Hy4‑preview,…