mirror of https://github.com/ggml-org/llama.cpp.git synced 2026-09-30 18:07:38 -05:00

Files

T

Pascal db00347a4b ci : fix Fusion / metal by adding glm5-next to MTL.csv (#29712 )

#27773 adds the glm5-next arch without its rows in the Metal fusion
baseline, so test-fusion --check fails on it. The rows come from
test-fusion --record on an M5 Max, and --check passes 270/270.

2026-09-30 09:50:23 +02:00

MTL.csv

ci : fix Fusion / metal by adding glm5-next to MTL.csv (#29712 )

2026-09-30 09:50:23 +02:00

README.md

tests : add fusion baseline README and broaden fusion CI triggers (#28893 )

2026-09-14 15:45:05 +03:00

README.md

Fusion baselines

Per-device baselines for test-fusion, one CSV per backend (e.g. MTL.csv). Rows are arch,moe,mode,label,count. Regenerate a CSV whenever fusion patterns change.

Update a baseline

cmake -B build -DCMAKE_BUILD_TYPE=Release -DGGML_METAL=ON   # enable the target backend
cmake --build build --config Release --target test-llama-archs --target test-fusion -j

rm -rf build-ci-models && mkdir -p build-ci-models
./build/bin/test-llama-archs -o build-ci-models

./build/bin/test-fusion --models build-ci-models --device MTL0 --record MTL.csv

Validate

./build/bin/test-fusion --models build-ci-models --device MTL0 --check MTL.csv

Non-zero exit means a row differs from the baseline. Use --model FILE to run a single architecture. Note --check only sees present rows — a fusion that stops matching is not reported, so diff the recorded CSV to catch removed patterns.