Backends (JIT and AOT) - Examples

Platform spec article

Backends (JIT and AOT) - Examples

Back to Backends (JIT and AOT) ◎ Open feature in platform map

Spec standingStandard

Owner

Piotr Mikstacki pmikstacki@cybernomad.it

Submitter

Piotr Mikstacki pmikstacki@cybernomad.it

Current document

ADRs (3)

1. 0001-feature-hub-authority Feature hub authority Accepted

   This feature hub owns normative MUST/SHOULD contract text for Backends (JIT and AOT).

   Context

   Sibling articles under this feature previously restated requirements in inconsistent forms.

   Decision

   This feature hub owns normative MUST/SHOULD contract text. Sibling articles must not redefine hub requirements and should link here for authority.

   Consequences

   Contract changes start on the hub or in linked ADRs, then propagate to articles and implementation anchors.

   Verification anchors

   • site/website/src/content/docs/platform-spec/compiler/build-pipeline/backends-jit-aot/index.mdx
   • article bundle under the same feature directory.

   Open full ADR page

2. 0002-spec-over-implementation-notes Specification over implementation notes Accepted

   Platform-spec text supersedes informal crate comments for Backends (JIT and AOT).

   Context

   Implementation crates accumulated informal notes that diverged from published contracts.

   Decision

   Normative platform-spec prose and ADRs under this feature supersede informal comments in implementation crates until explicitly migrated into spec text.

   Consequences

   Engineers file spec/ADR updates when behavior changes; crate comments are non-authoritative for conformance arguments.

   Verification anchors

   • compiler/crates/beskid_analysis/

   Open full ADR page

3. 0003-shared-codegen-artifact-backends Shared CodegenArtifact for JIT and AOT Accepted

   JIT and AOT must consume the same lowered artifact.

   Context

   Lowering produces one CodegenArtifact; backend selection happens after semantic gates complete.

   Decision

   Both JIT (beskid_engine::JitModule) and AOT link flows must accept the same schema fields from beskid_codegen without forking lowering.

   Consequences

   Backend-specific options attach at execution time; lowering stays single-path.

   Verification anchors

   • compiler/crates/beskid_engine/src/jit_module.rs
   • compiler/crates/beskid_codegen
   • compiler/crates/beskid_tests/src/runtime/jit.rs.

   Open full ADR page

Articles

• Backends (JIT and AOT) - Contracts and edge cases Required backend guarantees for output kinds, entrypoints, and shared lowering semantics. article Standard
• Backends (JIT and AOT) - Design model Backend responsibility split and shared artifact model for run and build commands. article Standard
• Backends (JIT and AOT) - Examples Example command outcomes for JIT execution and AOT output kinds. article Standard
• Backends (JIT and AOT) - FAQ and troubleshooting Troubleshooting for backend-specific build or run failures. article Standard
• Backends (JIT and AOT) - Flow and algorithm Ordered backend execution for run and build after lowering completes. article Standard
• Backends (JIT and AOT) - Verification and traceability Crate-level anchors and tests that verify backend divergence and shared lowering contract. article Standard

History

0 revisions (git unavailable at build; counts may be empty)

Open full history on GitHub

No commits recorded for this path.

Completeness

OKfeature · 0 SpecSection(s) · 1 H2 heading(s)

Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).

Related spec docs

• Feature
  Backends (JIT and AOT)

  Parent feature hub

• Domain
  Execution

  Runtime-side behavior

• beskid run success: JIT compiles and runs main, returning a formatted value string.
• beskid build --kind exe: AOT emits object, prepares runtime artifacts, then links executable.
• beskid build --kind object: AOT stops after object emission and skips link stage.
• Bad entrypoint: backend reports entrypoint resolution/signature diagnostic.