Repository navigation
Misc. bug: M1 Pro 8gb: the CLIP graph uses unsupported operators by the backend #21941
Copy link
Copy link
Closed
Closed
Copy link
Labels
Apple Metalhttps://en.wikipedia.org/wiki/Metal_(API)https://en.wikipedia.org/wiki/Metal_(API)bug-unconfirmedmacosIssues specific to macOSIssues specific to macOS
Description
Name and Version
Getting the following when running Gemma4 E2B it Q4_M (unsloth quant) + mmproj-BF16 on an M1 Pro 8gb
warmup: flash attention is enabled
warmup: *****************************************************************
warmup: WARNING: the CLIP graph uses unsupported operators by the backend
warmup: the performance will be suboptimal
warmup: list of unsupported ops (backend=MTL0):
warmup: ROLL: type = f32, ne = [128 8 1512 1]
warmup: ROLL: type = f32, ne = [128 8 1512 1]
warmup: ROLL: type = f32, ne = [754 1024 1 1]
warmup: ROLL: type = f32, ne = [128 8 1512 1]
warmup: ROLL: type = f32, ne = [128 8 1512 1]
warmup: ROLL: type = f32, ne = [754 1024 1 1]
warmup: ROLL: type = f32, ne = [128 8 1512 1]
warmup: ROLL: type = f32, ne = [128 8 1512 1]
warmup: ROLL: type = f32, ne = [754 1024 1 1]
warmup: ROLL: type = f32, ne = [128 8 1512 1]
warmup: ROLL: type = f32, ne = [128 8 1512 1]
warmup: ROLL: type = f32, ne = [754 1024 1 1]
warmup: ROLL: type = f32, ne = [128 8 1512 1]
warmup: ROLL: type = f32, ne = [128 8 1512 1]
warmup: ROLL: type = f32, ne = [754 1024 1 1]
warmup: ROLL: type = f32, ne = [128 8 1512 1]
warmup: ROLL: type = f32, ne = [128 8 1512 1]
warmup: ROLL: type = f32, ne = [754 1024 1 1]
warmup: ROLL: type = f32, ne = [128 8 1512 1]
warmup: ROLL: type = f32, ne = [128 8 1512 1]
warmup: ROLL: type = f32, ne = [754 1024 1 1]
warmup: ROLL: type = f32, ne = [128 8 1512 1]
warmup: ROLL: type = f32, ne = [128 8 1512 1]
warmup: ROLL: type = f32, ne = [754 1024 1 1]
warmup: ROLL: type = f32, ne = [128 8 1512 1]
warmup: ROLL: type = f32, ne = [128 8 1512 1]
warmup: ROLL: type = f32, ne = [754 1024 1 1]
warmup: ROLL: type = f32, ne = [128 8 1512 1]
warmup: ROLL: type = f32, ne = [128 8 1512 1]
warmup: ROLL: type = f32, ne = [754 1024 1 1]
warmup: ROLL: type = f32, ne = [128 8 1512 1]
warmup: ROLL: type = f32, ne = [128 8 1512 1]
warmup: ROLL: type = f32, ne = [754 1024 1 1]
warmup: ROLL: type = f32, ne = [128 8 1512 1]
warmup: ROLL: type = f32, ne = [128 8 1512 1]
warmup: ROLL: type = f32, ne = [754 1024 1 1]
warmup: flash attention is enabled
warmup: please report this on github as an issue
warmup: ref: https://github.com/ggml-org/llama.cpp/pull/16837#issuecomment-3461676118
warmup: *****************************************************************
Full llama-server command:
llama-server -m ./models/gemma-4-E2B-it-Q4_K_M.gguf \
--ctx-size 4096 \
--fit-target 512 \
--flash-attn on \
--cache-type-k q4_0 \
--cache-type-v q4_0 \
--parallel 1 \
--temp 0.3 \
--top-k 64 \
--top-p 0.95 \
--frequency-penalty 1.0 \
--repeat-penalty 1.1 \
--mmproj ./models/mmproj-BF16.gguf \
--image-min-tokens 300 \
--image-max-tokens 512 \
--host 0.0.0.0 \
--port 8080 --webui-mcp-proxy --webui-config-file ./uiConfig.json
full logs: unsupported-ops.log
ref: #16837 (comment)
Operating systems
Mac
Which llama.cpp modules do you know to be affected?
llama-server
Command line
llama-server -m ./models/gemma-4-E2B-it-Q4_K_M.gguf \
--ctx-size 4096 \
--fit-target 512 \
--flash-attn on \
--cache-type-k q4_0 \
--cache-type-v q4_0 \
--parallel 1 \
--temp 0.3 \
--top-k 64 \
--top-p 0.95 \
--frequency-penalty 1.0 \
--repeat-penalty 1.1 \
--mmproj ./models/mmproj-BF16.gguf \
--image-min-tokens 300 \
--image-max-tokens 512 \
--host 0.0.0.0 \
--port 8080 --webui-mcp-proxy --webui-config-file ./uiConfig.jsonProblem description & steps to reproduce
Run Gemma4 E2B Q4_M Unsloth on M1 Pro 8gb
First Bad Commit
No response
Relevant log output
Full logs unsupported-ops.log
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Apple Metalhttps://en.wikipedia.org/wiki/Metal_(API)https://en.wikipedia.org/wiki/Metal_(API)bug-unconfirmedmacosIssues specific to macOSIssues specific to macOS
Activity
kushagharahi commentedon Apr 16, 2026
bug fixed