14.7 CLIF and debug
Inspect Cranelift IR with beskid clif and debug flags without guessing lowering.
CLIF and debug
When lowering misbehaves, reading Rust alone is masochism. beskid clif dumps Cranelift IR so you can correlate machine intent with source.
Reference: beskid clif.
Typical uses:
- Verify spawn/fiber lowering produced expected blocks
- Compare JIT vs AOT IR for the same function
- Attach IR to bug reports with the spec/feature link
Debug flags
Section titled “Debug flags”Compiler logging and phase traces align with beskid_pipeline phase IDs—see Pipeline composition and book chapter 02 tooling — logging for operator-facing flags.
Spec anchors
Section titled “Spec anchors”What CLIF is not
Section titled “What CLIF is not”- Not a substitute for semantic diagnostics—fix types first.
- Not a public stability contract for third-party tools—IR details may shift with Cranelift updates.