Shared CodegenArtifact for JIT and AOT
Platform spec ADR
Shared CodegenArtifact for JIT and AOT
Spec standingStandard
- Backends (JIT and AOT) - Contracts and edge cases Required backend guarantees for output kinds, entrypoints, and shared lowering semantics.
- Backends (JIT and AOT) - Design model Backend responsibility split and shared artifact model for run and build commands.
- Backends (JIT and AOT) - Examples Example command outcomes for JIT execution and AOT output kinds.
- Backends (JIT and AOT) - FAQ and troubleshooting Troubleshooting for backend-specific build or run failures.
- Backends (JIT and AOT) - Flow and algorithm Ordered backend execution for run and build after lowering completes.
- Backends (JIT and AOT) - Verification and traceability Crate-level anchors and tests that verify backend divergence and shared lowering contract.
0 revisions (git unavailable at build; counts may be empty)
No commits recorded for this path.
Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).
Context
Section titled “Context”Lowering produces one CodegenArtifact; backend selection happens after semantic gates complete.
Decision
Section titled “Decision”Both JIT (beskid_engine::JitModule) and AOT link flows must accept the same schema fields from beskid_codegen without forking lowering.
Consequences
Section titled “Consequences”Backend-specific options attach at execution time; lowering stays single-path.
Verification anchors
Section titled “Verification anchors”compiler/crates/beskid_engine/src/jit_module.rscompiler/crates/beskid_codegencompiler/crates/beskid_tests/src/runtime/jit.rs.