Files
zig/stage0
Motiejus 69a0486232 sema: fix shard simulation, bump num_passing 61→67
Fix the IP shard simulation to work for all main analysis, not just
during ensureFullMemoizedStateC. This fixes tests 61-66 (inline fn
tests and non-inline tests that reference types from preamble builtins).

Key changes:
- Move skip_dedup activation to the end of the preamble (after
  analyzeMemoizedStateC + start.zig comptime). Previously it was only
  set during ensureFullMemoizedStateC, missing tests that don't
  trigger full builtin resolution.
- Expand cc_keep range by 1 entry to include the CC ptr_nav that
  AddressSpace resolution creates as a side effect (fixing the
  1-entry excess for inline function tests).
- Remove skip_dedup clearing from ensureFullMemoizedStateC (it stays
  active for the entire main analysis).

Next blocker: test 67 (shl_sat.zig) — the shift amount type (u6 for
u32 operand) is not created. C stores the shift amount as u32(1)
instead of u6(1). Need to port shift amount type coercion.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-02 17:54:04 +00:00
..
2026-02-20 12:33:48 +02:00
2026-02-26 00:45:27 +02:00
2026-02-17 10:56:11 +00:00

About

zig0 aspires to be an interpreter of zig 0.15.2 written in C.

Except for the lexer (written by hand by yours truly), it's been written by an LLM.

The goal of stage0 is to be able to implement enough zig to be able to build zig1.wasm. For that we need:

  1. Lexer: DONE, written by hand by yours truly in late 2024.
  2. Parser: DONE, written mostly by an LLM.
  3. AstGen: DONE, written fully by an LLM.
  4. Sema: in progress.

Testing

Quick test:

zig build fmt-zig0 test-zig0

Static analysis (takes a while, run separately):

zig build lint-zig0

More elaborate (tries all compilers + static analysis + ReleaseSafe):

zig build all-zig0 -Doptimize=ReleaseSafe

Most elaborate, takes >10m:

zig build all-zig0 -Doptimize=ReleaseSafe -Dvalgrind |& grep -v Warning

Debugging tips

Test runs infinitely? Build the test program executable:

$ zig build test-zig0 -Dzig0-no-exec

And then run it, capturing the stack trace:

gdb -batch \
    -ex "python import threading; threading.Timer(1.0, lambda: gdb.post_event(lambda: gdb.execute('interrupt'))).start()" \
    -ex run \
    -ex "bt full" \
    -ex quit \
    zig-out/bin/test

You are welcome to replace -ex "bt full" with anything other of interest.

Float Handling

Float literals are parsed with strtold() (C11 standard, portable). On x86-64 Linux, long double is 80-bit extended precision (63 fraction bits).

When a float doesn't round-trip through f64, it's emitted as f128 (ZIR float128 instruction). The 80-bit extended value is converted to IEEE 754 binary128 encoding by bit manipulation — both formats share the same 15-bit exponent with bias 16383. The top 63 of binary128's 112 fraction bits come from the 80-bit value; the bottom 49 are zero-padded.

This means float128 literals lose ~49 bits of precision compared to the upstream Zig implementation (which uses native f128). This is acceptable because stage0 is a bootstrap tool — the real Zig compiler re-parses all source with full f128 precision in later stages. The test comparison mask in astgen_test.zig skips float128 payloads to account for this.

Previous approach used __float128/strtof128 (GCC/glibc extensions) for full precision, but these are not portable to TCC and other C11 compilers.