gguf-tools splicer cannot read the MXFP4 GGUF this repo publishes (unsupported GGML tensor type 39)
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 92/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Quiet
- Domain
- machine-learning, tooling
Research direction
Open gguf-tools/mixed/splice_mixed_expert_layers_gguf.py and locate GGML_QUANT_SIZES; compare the MXFP4 values with ds4.c:2052. Run the reported --dry-run splice for layers 25-42, then confirm type 39 is accepted and the selected donor tensors and payload summary complete without the unsupported-type error.
Written by the indexing model from the issue text.
Description
The Flash MXFP4 GGUF (ds4f-mxfp4) cannot be used as a donor or base with gguf-tools/mixed/splice_mixed_expert_layers_gguf.py, because its GGML_QUANT_SIZES table has no entry for type 39.
error: unsupported GGML tensor type 39; add it to GGML_QUANT_SIZES
Everything else in the splicer already handles it correctly — it deliberately does not require base and donor tensor types to match, and it writes each tensor's own ggml_type through. Only the block-size table is missing an entry.
One-line fix, using the values from ds4's own table at ds4.c:2052 ([39] = {"mxfp4", 32, 17}):
GGML_QUANT_SIZES = {
...
26: (1, 4, "I32"),
+ 39: (32, 17, "MXFP4"),
}
Verified locally with --dry-run, splicing MXFP4 routed experts for layers 25-42 onto the IQ2XXS/Q2_K hybrid base:
selected donor tensors: 54
selected donor types: MXFP4:54
base tensor payload: 90.88 GiB
mixed tensor payload: 107.76 GiB
Motivation, in case it is useful: this produces a quant sized for a single 128 GB Mac. The published Flash quants are 80.8 / 90.9 GiB (fit, leaving ~21 GiB of the 112 GiB wired limit unused) then jump to 145.3 / 153.3 GiB (do not fit). Splicing MXFP4 experts into the upper layers fills that gap at 107.76 GiB.
Happy to open a PR if useful.
- Dominant language
- C
- Stars
- 22.5k
- Forks
- 2.2k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 5
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from antirez/ds4
-
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
CUDA single GPU: --gpu-vram + --ssd-streaming refused as "multi-GPU placement" (misleading message) Open
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Similar issues
-
level/task module/gcp type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
docs
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
P3 sonic-vpp
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sonic-net/sonic-buildimage#29662 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 94/100
spack/spack-packages#6586 ·
-
category:port-update
Difficulty 2/5 1-3 hours Newbie friendliness 72/100