How exo-lang/exo works
Exo is a Python-based exocompiler for writing and scheduling loop-oriented tensor procedures, then generating C and headers for target hardware. The principal workflow is author a procedure, transform it with scheduling operations, and compile it. Its internal layers include Python-to-LoopIR parsing, IR rewrites and analyses, and target-aware C code generation; memory models and hardware platform support provide important additional capabilities. Several relationships below are documented by the README or SOURCE INDEX; unsampled implementation details are not inferred.
Main entry points: LoopIR.py LoopIR · API.py Procedure API · LoopIR_compiler.py C Compiler · scheduling.py Scheduling Library
Components 21
Authoring and API
- Exocc CLI
src/exo/main.py - Procedure API
src/exo/API.py - Python Parser
src/exo/frontend/pyparser.py - Fragment Parser
src/exo/frontend/parse_fragment.py
IR and Scheduling
- Scheduling API
src/exo/API_scheduling.py - Cursor API
src/exo/API_cursors.py - Scheduling Library
src/exo/stdlib/scheduling.py - Schedule Compositions
src/exo/stdlib/stdlib.py - IR Inspection
src/exo/stdlib/inspection.py - LoopIR
src/exo/core/LoopIR.py - IR Rewrites
src/exo/rewrite/LoopIR_scheduling.py
Analysis and Codegen
- Effect Analysis
src/exo/rewrite/new_eff.py - Range Analysis
src/exo/rewrite/range_analysis.py - C Compiler
src/exo/backend/LoopIR_compiler.py
Memory and Targets
- Memory Models
src/exo/core/memory.py - Target Memories
src/exo/libs/memories.py - Gemmini Platform
src/exo/platforms/gemmini.py - NEON Platform
src/exo/platforms/neon.py - x86 Platform
src/exo/platforms/x86.py
Other components
- Exo Developer
- Generated C and Header
Connections 26
- Exo Developer → Exocc CLI: runs compiler
README.md - Exo Developer → Procedure API: defines procedures
- Exocc CLI → Procedure API: loads API
src/exo/main.py - Exocc CLI → Generated C and Header: emits C and header
README.md - Python Parser → LoopIR: builds IR
src/exo/frontend/pyparser.py - Fragment Parser → Python Parser: uses parser
src/exo/frontend/parse_fragment.py - Fragment Parser → LoopIR: builds fragments
src/exo/frontend/parse_fragment.py - Scheduling Library → Scheduling API: exposes operations
src/exo/stdlib/scheduling.py - Scheduling Library → Cursor API: uses cursors
src/exo/stdlib/scheduling.py - Schedule Compositions → Scheduling Library: composes schedules
src/exo/stdlib/stdlib.py - Schedule Compositions → IR Inspection: uses inspection
src/exo/stdlib/stdlib.py - IR Rewrites → LoopIR: rewrites IR
src/exo/rewrite/LoopIR_scheduling.py - IR Rewrites → Effect Analysis: uses effects
src/exo/rewrite/LoopIR_scheduling.py - IR Rewrites → Range Analysis: uses ranges
src/exo/rewrite/LoopIR_scheduling.py - LoopIR → Memory Models: represents memory
src/exo/core/LoopIR.py - C Compiler → LoopIR: compiles IR
src/exo/backend/LoopIR_compiler.py - C Compiler → Range Analysis: uses ranges
src/exo/backend/LoopIR_compiler.py - C Compiler → Memory Models: generates memory code
src/exo/backend/LoopIR_compiler.py - C Compiler → Generated C and Header: emits C
- Target Memories → Memory Models: implements memories
src/exo/libs/memories.py - Gemmini Platform → Target Memories: uses memories
src/exo/platforms/gemmini.py - Gemmini Platform → Scheduling Library: uses schedules
src/exo/platforms/gemmini.py - Gemmini Platform → Procedure API: uses procedure API
src/exo/platforms/gemmini.py - NEON Platform → Procedure API: uses procedure API
src/exo/platforms/neon.py - x86 Platform → Target Memories: uses memories
src/exo/platforms/x86.py - x86 Platform → Procedure API: uses procedure API
src/exo/platforms/x86.py