code wiki / _hdl_build / nx_nested_loop_ref.nx

nx_nested_loop_ref.nx

buildroot/runtime/_hdl_build/nx_nested_loop_ref.nx

3655 B74 linesdepth 3pulls 3 transitivereach 0 importersview sourcekind tool

docs dependencies structs consts functions

about

nx_nested_loop_ref.nx -- DIFFERENTIAL SPEC CHECK: does the LANGUAGE's PRODUCTION compiler (nx_cc, which builds every organ) compute nested while-loops the way I expect? This is the reference oracle for "is the nxc nested-loop failure a BUG or a DESIGN CHOICE". Runs the EXACT nested-loop programs nxc miscompiled, on nx_cc (this very build path), and prints the results. If nx_cc gives 25/25, nested loops ARE supported+correct in NishiLang -> nxc has a real bug. If nx_cc disagrees, it's a design/semantics difference and my expectation was wrong. expect_exit: 0

dependencies 2 imports · 0 importers

imports: nx_syscalls.nxnx_g_puts_lib.nx

imported by: nobody (leaf or entry point)

call flow from main pre-order; caps 40 nodes / depth 6 declared; ↻ = already shown

structs

none

consts

none

functions

9	func g_pn(v: i64) -> i64 { let b: *u8=sys_mmap(28); var x: i64=v; if x==0{b[0]=48;sys_write(1,b,1);return 0} var d: i64=0; var y: i64=x; while y>0{d=d+1;y=y/10} var i: i64=d-1; y=x; while i>=0{b[i]=(48+(y%10)) as u8;y=y/10;i=i-1} sys_write(1,b,d); return 0 } called by 1: main calls 2: sys_mmap sys_write
10	func ck(name: u8, c: i64) -> i64 { if c==1 { g_puts(" PASS " as u8) } else { g_puts(" FAIL " as u8) } g_puts(name); g_puts("\n" as u8); return c } called by 1: main calls 1: g_puts
13	func nested_inner_var() -> i64 called by 1: main
27	func nested_func_var() -> i64 called by 1: main
42	func nested_sum() -> i64 called by 1: main
56	func main() -> i64 calls 7: g_puts nested_inner_var g_pn ck nested_func_var nested_sum+1