LOOM is the successor design to the legacy design for the current Fabric Compiler effort.
This directory contains the implementation-anchor specifications for LOOM.
When the legacy design and LOOM differ, LOOM documents in this directory take
precedence for future work under this repository.
| Spec |
Description |
| spec-fabric.md |
Fabric dialect overview and operation taxonomy |
| spec-fabric-config_mem.md |
Unified config bitstream model, slice ordering, and per-resource packing |
| spec-fabric-function_unit.md |
fabric.function_unit and fabric.mux semantics |
| spec-fabric-fifo.md |
fabric.fifo structure, legality, and runtime bypass config |
| spec-fabric-tag.md |
fabric.add_tag, fabric.map_tag, and fabric.del_tag |
| spec-fabric-memory-interface.md |
Extmemory-facing routing, tagged multi-port memory, and memory region contract |
| spec-fabric-spatial_pe.md |
fabric.spatial_pe container, mux/demux model, config layout |
| spec-fabric-spatial_sw.md |
fabric.spatial_sw, decomposable routing, route-table semantics |
| spec-fabric-temporal_pe.md |
fabric.temporal_pe structure, slot encoding, and register model |
| spec-fabric-temporal_sw.md |
fabric.temporal_sw tag-matching route-table semantics |
| Spec |
Description |
| spec-viz.md |
Visualization architecture and mapping-on rendering requirements |
| Spec |
Description |
| spec-simulation.md |
Standalone simulation model, trace, and validation contract |
| spec-runtime-mmio.md |
SimSession lifecycle, host driver API, and MMIO control model |
| spec-gem5.md |
gem5 integration, baremetal host execution, and device boundary |
| spec-trace.md |
Trace and performance schema for standalone and gem5-backed runs |
| spec-validation.md |
Acceptance matrix and end-to-end validation contract |
- This is the first LOOM-native spec set. It intentionally focuses on the
currently active architecture and the most important implementation anchors.
- Backend realization, standalone simulation, and gem5 integration specs
are included above and continue to evolve.
- Several currently observed mapper and visualization gaps are intentionally
captured here as normative requirements so later implementation work can
converge against explicit specs.
- Pure project-management content such as implementation batches remains better
suited to planning notes than to normative spec documents.