LEGACY DOCS · 12.3Stable is 13.2. This page stays because it still owns historical or unchanged contracts.CURRENT 13.2 →
RELEASE LINE13.2 HISTORICAL13.1 PREDECESSOR13.0 PREVIOUS12.4 NATIVE MIRARCHIVE

LEGACY DOCS · 12.3

PAGE ROLE · BEGINNER EXPLANATION

THE V12.3 VM, WITHOUT THE FOG

A VM is just another machine contract. The useful question is where instructions live, where values live, and who moves control next.

00 before v12.3

Nested VM execution could enter bytecode execution again for a DByte call. v12.3 removes that shape from production execution.

10 the new shape

CONCRETE HIR
    -> CANONICAL BYTECODE BODY
       instructions[]
       dense frame slots
       finalized branch indices
       direct function IDs

EXECUTOR
    instruction pointer
    reusable frame stack
    one dispatch loop

Each concrete function owns one flat instruction vector and one deterministic frame layout. A DByte call pushes an explicit frame instead of recursively starting another dispatcher.

20 why this matters

Control flow becomes cheaper to execute and easier to inspect. The call depth limit remains explicit: at most 16 active DByte calls, checked when the call happens.

30 O0 and O1

O0 and O1 use the same bytecode representation and the same dispatcher. O1 may apply side-effect-safe optimizations, but it does not get permission to move errors, skip bounds checks, break borrows, or forget Drop.

MACHINE NOTE. Faster is useful. Faster with different semantics is a bug wearing running shoes.

40 exact contract

READ THE NORMATIVE V12.3 CONTRACT