Motiejus
e5f71beb02
The C parser uses OPT() macro which stores UINT32_MAX as the "none" sentinel for optional AST node indices in extra_data. The rlExpr (AstRlAnnotate) and exprRl functions were checking `!= 0` for these fields, treating UINT32_MAX as a valid node index and causing segfaults. Fixed optional field checks for fn_proto_one, fn_proto extra data (param, align, addrspace, section, callconv), while cont_expr, global_var_decl type_node, and slice_sentinel end_node. Also added behavior test corpus files and FAIL: diagnostic to the corpus test runner. 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 build fmt-zig0 test-zig0
Full test and static analysis with all supported compilers and valgrind (run before commit, takes a while):
zig build all-zig0 -Dvalgrind
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.