Target matrix
General semantics are shared while privileged capabilities remain profile-specific.
DByte 12.0 · Reference
Contract§
| Capability | Hosted | VM | i686 none | i686 user | Evidence |
|---|---|---|---|---|---|
| Canonical HIR | SUPPORTED | SUPPORTED | SUPPORTED | SUPPORTED | HIR corpus |
| Generics, enums, ownership | SUPPORTED | SUPPORTED | SUPPORTED | SUPPORTED | V12 corpus |
| native.* and interrupts | NOT SUPPORTED | NOT SUPPORTED | SUPPORTED (KERNEL) | NOT SUPPORTED | Systems boundary |
| User syscalls | NOT SUPPORTED | NOT SUPPORTED | NOT SUPPORTED | SUPPORTED | User-process contract |
Mechanics§
The matrix distinguishes semantic support from target privilege. Canonical language constructs are shared, while native CPU operations, interrupt declarations and user syscalls are gated by profile.
Validation and failure§
SUPPORTED means the stated semantics/backend lowering exist for that profile; it does not imply deferred owned runtime types or a new platform target.
Evidence and boundary§
Each positive cell is exercised by a corpus build, and each privileged boundary has explicit negative tests. Direct evidence links are exposed from the capability table where a public documentation/proof entrypoint exists.
Host distribution matrix§
| Host | v12.0 binary release |
|---|---|
| Windows x64 | SUPPORTED |
| Linux x86_64 | NOT RELEASED |
| macOS | NOT RELEASED |
Platform support explains why host support and target support are separate claims.
Historical future-target ledger (as of v12.0)§
| Target | v12.0 | Roadmap at v12.0 |
|---|---|---|
x86_64-dbyte-none | DEFERRED | PROPOSED v12.3 |
x86_64-dbyte-windows | DEFERRED | PROPOSED v12.3 |
x86_64-dbyte-linux | DEFERRED | PROPOSED v12.3 |
HISTORICAL PLANNING CONTEXT: these targets were proposed for v12.3 when v12.0 shipped. The roadmap is now superseded; all three modern x86_64 targets shipped in v12.2.0. The table is retained only to describe the v12.0 planning state.