ERR/E3.0 (slice 3b): comptime trace resolution
#run failures now print the same `func at file:line:col` trace as runtime, resolved in-process via the interpreter's IR/source tables. - Read-side context-split op `.trace_resolve` (mirror of .trace_frame), lowered from a name-recognized `__trace_resolve_frame(u64) -> Frame`. - emit_llvm: inttoptr the operand to *Frame + load (the value .trace_frame stamped in). - interp: unpack (func_id << 32 | span.start); resolve func/file from module.functions and line/col via SourceLoc.compute over a new source_map (setSourceMap wired at every production interp site). - trace.sx: frame_at -> u64; to_string routes each frame through __trace_resolve_frame, so one source works in both machines. Compiled path behavior unchanged (243/244/247 identical; it now loads via the op). New examples/253-comptime-trace.sx exercises the comptime path. Gates: zig build, zig build test, run_examples.sh -> 291 passed.
This commit is contained in:
1
tests/expected/253-comptime-trace.exit
Normal file
1
tests/expected/253-comptime-trace.exit
Normal file
@@ -0,0 +1 @@
|
||||
0
|
||||
5
tests/expected/253-comptime-trace.txt
Normal file
5
tests/expected/253-comptime-trace.txt
Normal file
@@ -0,0 +1,5 @@
|
||||
comptime caught Bad
|
||||
error return trace (most recent call last):
|
||||
leaf at 253-comptime-trace.sx:15:5
|
||||
mid at 253-comptime-trace.sx:19:5
|
||||
--- build done ---
|
||||
Reference in New Issue
Block a user