RepoJournal
Local LLMs Local LLMs
99 wires and counting

$ follow Local LLMs

Keep up with Local LLMs in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-10-25
stories 188

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

MoE expert masking lands across every llama.cpp backend

By RepoJournal · Filed · About Local LLMs · Composed from the cited sources · methodology

llama.cpp taught mul_mat_id to read a -1 index as "skip this computation" in one unfenceable sweep across all backends, opening the door to the expert-mask MoE pattern and to DeepSeek-V4.1-Flash support in the same day.

ggml : allow MUL_MAT_ID -1 index to skip the computation ggml-org/llama.cpp

by ngxson

A -1 index passed to mul_mat_id now means "skip the computation," which enables an expert mask like the PyTorch MoE implementation. ngxson notes the change could not be gated behind a graph build-time condition, so every backend was touched at once, and states plainly that "code is 100% AI-generated." The motivating models are ones with "small" and "big" expert tiers.

model: DSV4.1 flash (#31086) ggml-org/llama.cpp

by Aman Gupta

llama.cpp gains DeepSeek-V4.1-Flash (deepseek41): MXFP8 is removed, the Engram table converts to BF16, compressed-KV read layers are computed once in the cache, and Engram rows are gathered in-graph rather than on the host. The Engram hash constants now live in hparams.ple_*, one module per Engram layer.

metal : remove mul_mm_id amax rescaling ggml-org/llama.cpp

by ggerganov

The Metal mul_mm_id kernel drops the amax rescaling of src1 added to prevent inf/NaN when MoE activations overflow f16. Since the MoE down projection is rescaled per expert-token in the compute graph, activations reach MUL_MAT_ID already in f16 range and the in-kernel rescale is redundant; ggerganov also notes the removed path was gated on GGML_PREC_F32 for src1, which nothing in the graph sets.

[Fix] [AMD] custom-allreduce: Stop registering oversized inputs in the deterministic all-reduce sgl-project/sglang

by vvagaytsev

On AMD GPUs, deterministic all-reduce (enabled by --enable-deterministic-inference, --rl-on-policy-target, or SGLANG_USE_1STAGE_ALLREDUCE=1) produced each GPU's own input instead of the sum whenever a single all-reduce exceeded the 16 MiB working buffer, which a normal prefill on a large model triggers. Each oversized call also permanently consumed an entry in a fixed-size table until the proce...

[ROCm][MLA][DCP] Drop VLLM_ROCM_AITER_MLA_DCP_VERIFY vllm-project/vllm

by xaguilar-amd

The remainder is housekeeping and narrow tuning: vLLM removes VLLM_ROCM_AITER_MLA_DCP_VERIFY so the DCP spec-decode verify kernel is picked heuristically with unchanged defaults, adds an opt-in MXFP4 int8-dot GEMV for gfx11 decode and indexer context parallelism for MiniMax-M3 behind --attention-config '{"indexer_cp": true}', while sglang moves the Marlin GPT-OSS SwiGLU onto a fused Triton kern...

Quick answers

What shipped in Local LLMs on October 25, 2026?
llama.cpp taught mul_mat_id to read a -1 index as "skip this computation" in one unfenceable sweep across all backends, opening the door to the expert-mask MoE pattern and to DeepSeek-V4.1-Flash support in the same day. In total, 89 commits, 89 pull requests, and 10 releases landed.
Who contributed to Local LLMs on October 25, 2026?
14 developers shipped this update, including dhiltgen, ngxson, danbev, Aman Gupta, allozaur, ggerganov, xiao-llm, and charxwu, and 6 more.
What were the notable Local LLMs updates?
ggml : allow MUL_MAT_ID -1 index to skip the computation, model: DSV4.1 flash (#31086), and metal : remove mul_mm_id amax rescaling.