Compile and debug StableHLO MLIR simulations through the Cranelift JIT backend.
npx skills add https://github.com/elodin-sys/elodin --skill elodin-cranelift
Please help me install this Agent Skill. Skill: elodin-cranelift Source: https://github.com/elodin-sys/elodin/tree/main/.cursor/skills/elodin-cranelift Command: npx skills add https://github.com/elodin-sys/elodin --skill elodin-cranelift
Working on Elodin's Cranelift JIT backend requires navigating a dual-ABI compiler pipeline, a StableHLO parser, a tensor runtime, and XLA reference comparisons, and this Skill consolidates the commands, file map, and debugging workflows needed to modify libs/cranelift-mlir/ correctly.
Ask the assistant to add a new StableHLO op to the Cranelift backend or to debug why a simulation example diverges from the XLA reference using the checkpoint diagnostic tool.
High-intent search queries and answers about installing and using this skill.
Add an Instruction variant in src/ir.rs, a parser arm in src/parser.rs, lowering arms in both lower_instruction and lower_instruction_mem in src/lower.rs, and a tensor runtime function in src/tensor_rt.rs if the op is N-dimensional. Then add golden tests in tests/ops.rs exercising both ABI paths and run cargo test -p cranelift-mlir.
Run the example with ELODIN_BACKEND=cranelift and ELODIN_CRANELIFT_DEBUG_DIR set to capture XLA reference and Cranelift outputs per tick. Then run the checkpoint_test comparator in release mode to compare outputs element-by-element and reduce the diverging output to a minimal tests/ops.rs reproducer.
Cranelift is the default CPU backend that compiles StableHLO MLIR to native code via a JIT, while jax-cpu uses XLA as the reference implementation for correctness. You can switch per-run with the ELODIN_BACKEND environment variable or the backend argument in Python.
Some JIT paths trip ptr::copy_nonoverlapping debug-mode UB checks, so try running with --release first. Complex sims can also overflow the stack, and NULL pointers in JIT code usually indicate a cross-ABI marshaling bug.
Dense hex constants over 1 MB are decoded as raw bytes and interned in a content-addressed cache under ELODIN_CACHE_DIR or ~/.cache/elodin/const-cache. The lowering registers them as imported JIT symbols so constants are not copied into the JIT arena, and CompiledModule must retain the cache handles to avoid dangling mmap pointers.
elodin-sysBuild and test the Elodin Python SDK with PyO3 bindings and JAX integration.
tabgabCompare simulation scalar results against saved baselines to detect regressions.
elodin-sysCapture nanosecond-resolution Tracy traces from the Elodin editor and simulation.
QuantumBFSConfigures and validates JAX backend environments for quantum simulation.
