Motiejus Jakštys
52bfd87de7
Three bugs found by auditing against upstream AstGen.zig/AstRlAnnotate.zig: 1. rlExpr: defer was recursing into nd.rhs (always 0) instead of nd.lhs (the actual deferred expression), so the RL annotation pass never visited defer bodies. 2. addEnsureResult: compile_error was missing from the noreturn instruction list, causing spurious ensure_result_used instructions to be emitted after @compileError calls. 3. blockExprExpr: force_comptime was derived from gz->is_comptime, but upstream blockExpr always passes force_comptime=false to labeledBlockExpr. This caused labeled blocks in comptime contexts to incorrectly emit BLOCK_COMPTIME + BREAK_INLINE instead of BLOCK + BREAK. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
About
zig0 aspires to be an interpreter of zig 0.15.1 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 build fmt test
Full test and static analysis with all supported compilers and valgrind (run before commit, takes a while):
zig build -Dvalgrind
Debugging tips
Test runs infinitely? Build the test program executable:
$ zig build test -Dno-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.