Skip to content

chore: bump mlx-swift for compiled kernel dtype fix - #193

Merged
solderzzc merged 1 commit into
mainfrom
chore/bump-mlx-swift-kernel-dtypes
Sep 26, 2026
Merged

solderzzc merged 1 commit into
mainfrom
chore/bump-mlx-swift-kernel-dtypes

Conversation

@solderzzc

Copy link
Copy Markdown
Member

Bumps mlx-swift from 384de38 to 1a2b3af to pick up SharpAI/mlx-swift#19 (the only change in that range). Compiled kernel names now include the input dtypes. Before, two graphs that differed only in input dtype (for example bf16 and f16) shared one Metal library, so the second graph ran the first graph's kernel. This is the upstream fix ml-explore/mlx#3427, applied ahead of the upstream sync.

mlx-swift-lm is unchanged (7cc37a0).

Tested on M5 Pro:

  • swift build -c release and swift build --build-tests
  • TurboQuant C++ test: 9/9
  • SwiftLMTests: 194 tests, 0 failures
  • SwiftBuddyTests: 127 tests, 9 skipped, 0 failures
  • Server smoke test with mlx-community/Qwen3.5-0.8B-4bit --turbo-kv: single-turn and multi-turn chat answer correctly. Without --turbo-kv, text requests to this model fail with unsupportedBatchContinuation on main as well. That is a separate issue and not related to this bump.

AI usage: Claude Code (Claude Opus 5.5) made the bump, ran the tests and wrote this description.

🤖 Generated with Claude Code

Picks up SharpAI/mlx-swift#19: compiled kernel names now include the
input dtypes, so graphs that differ only in input dtype no longer share
one Metal library.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@solderzzc
solderzzc merged commit c9566c8 into main Sep 26, 2026
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant