Compiler Artifacts

Current implementation evidence: README.html, docs/compiler.html,

docs/object-format.html, docs/archive-format.html, and docs/linker.html.

OISA

0x0 source compiles to OISA. The self-host chain compares generated stages to

prove compiler stability.

Example command:

./bin/zero oisa examples/add.0x0

Native Compatibility Compiler

bin/zero-native is built from compiler/compat-main.0x0. It supports

compatibility paths for C, native executable builds, object builds, ELF output,

and compiler artifact generation.

Object And Archive Paths

0x0 has documented object, archive, and linker surfaces. Use the object,

archive, and linker docs for format details and current limits.

Direct ELF Path

The current direct ELF backend supports the documented slice. It is not a

promise that every future language feature is available through every backend.

Practical Rule

When documenting compiler behavior, state the backend and artifact path. OISA,

C compatibility, object, archive, linked executable, and direct ELF paths have

different current coverage.