Motiejus
8a6aa3583b
Implement generic function body analysis for runtime calls to functions with comptime parameters. When a generic function like normalize(comptime T: type, p: *T) is called at runtime, the C sema now produces a monomorphized function entry (e.g. normalize__anon_42) matching upstream Zig's finishFuncInstance behavior. Key changes: - analyzeFuncBodyAndRecord accepts optional call_args for comptime param mapping: comptime params get mapped to resolved values from the call site instead of generating ARG instructions - Runtime params use original param index (not renumbered) to match Zig - Deduplication handles __anon_NNN suffix for repeated generic calls - sema_test.zig strips __anon_NNN suffixes for name comparison since IP indices differ between C and Zig compilers Enables sema tests 82-88 (num_sema_passing: 82 → 89, all tests pass). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
About
zig0 aspires to be an interpreter of zig 0.15.2 written in C.
This is written with help from LLM:
- Lexer:
- Datastructures 100% human.
- Helper functions 100% human.
- Lexing functions 50/50 human/bot.
- Parser:
- Datastructures 100% human.
- Helper functions 50/50.
- Parser functions 5/95 human/bot.
- AstGen: TBD.
Testing
Quick test:
./zig-out/bin/zig build fmt-zig0 test-zig0
Static analysis (takes a while, run separately):
./zig-out/bin/zig build lint-zig0
More elaborate (tries all compilers + static analysis + ReleaseSafe):
./zig-out/bin/zig build all-zig0 -Doptimize=ReleaseSafe
Most elaborate, takes >10m:
./zig-out/bin/zig build all-zig0 -Doptimize=ReleaseSafe -Dvalgrind |& grep -v Warning
Debugging tips
Test runs infinitely? Build the test program executable:
$ ./zig-out/bin/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.
Rebuilding zig
If you need to rebuild zig-out/bin/zig for some reason, here's how:
~/code/zig-bootstrap/out-0.15.2/zig-x86_64-linux-musl-x86_64_v3/zig build \
--zig-lib-dir lib/ -Dtarget=x86_64-linux-musl -Dcpu=x86_64_v3 \
-Dstatic-llvm --search-prefix \
$HOME/code/zig-bootstrap/out-0.15.2/x86_64-linux-musl-x86_64_v3/ \
-Ddebug-extensions=true -Dlog=false -Doptimize=ReleaseSafe