Repository navigation
Conversation
cerisier
marked this pull request as ready for review
October 16, 2026 19:24
zcbenz
force-pushed
the
mlx/cpu-jit-cache
branch
from
October 19, 2026 00:56
b5e7ef5 to
4063c21
Compare
zcbenz
force-pushed
the
mlx/cpu-jit-cache
branch
from
October 19, 2026 03:42
4063c21 to
9b5df75
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add
MLX_CPU_CACHE_DIRso hermetic build and test setups such as Bazel can explicitly control where CPU JIT artifacts are stored.I reused a similar approach for MLX_PTX_CACHE_DIR for CUDA so hopefully this makes ense.