aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* analyzer: use-after-end messages name the borrower, the owner and how the ↵Gravatar zinc 12 days12-21/+110
| | | | owner ended (freed, moved, .d parameter, push, global, reassignment), with fixtures
* merge work/stdio: std.Io and one-level module completionGravatar zinc 12 days11-10/+184
|\
| * lsp: prefer the rt import fix when a library group wraps the same nameGravatar zinc 12 days1-1/+2
| |
| * lsp: complete a module path one level at a time (std. lists groups, ↵Gravatar zinc 12 days2-5/+36
| | | | | | | | std.File. and std.Io. their members)
| * std: add std.Io (print, println, nl, put_*, put_f, get_c, eof, read, ↵Gravatar zinc 12 days10-4/+146
|/ | | | getline) with test, learn example and docs
* xref: baseline records the prover's writers of ft_ln (bin, kw_for), xub and ↵Gravatar zinc 12 days1-0/+3
| | | | xubat (bin)
* todo: overnight freelist-inline done-gate met with trees timingsGravatar zinc 13 days1-1/+3
| | | | | | Mark native freelist pop/push inline done (c31a07d/63ff1aa), record x86-64 jit trees ~3× win and llvm/C comparison ratios; clear the overnight still-open line.
* x86-64 jit: inline new_k, recycle_leaf and own fast paths, in o3 regions and ↵Gravatar zinc 13 days6-7/+306
| | | | | | | | | | | | | | plain blocks a call to rt.new_k / rt.recycle_leaf with a constant class, or to rt.own, does its class-list pop or push (or owner store) inline and goes on after the call; an empty list, memdebug, a held range, a block outside memory, a translated word or a type/class mismatch takes the ordinary call. in a region this replaces the o3_invoke round trip. o3 frees of leaf objects now use recycle_leaf too (new_k stamps the type inside o3 since b86db60). ZYNOFASTALLOC=1 turns it off; ZYPERFMAP=1 writes a perf map of translated code. tests/programs/o3_freelist.zc: reuse, zeroing, an empty list, untyped neighbours, memdebug; jit vs ZYNOFASTALLOC vs ZYO3INTERP.
* rt: recycle, new_k and own without helper calls or || chainsGravatar zinc 13 days1-18/+58
| | | | | | | | | | perf (ZYPERFMAP) on plain trees new/free showed recycle, new_k and own taking about 70% of the time, mostly in calls to isobj, paylen, bdrop, bclass and fpush and in the truth values plain code builds for && and ||. recycle writes isobj, paylen and the class-list push out, calls scan_ptr only for 8 or more words left, and own and new_k test with nested ifs. frame_control grows to 22 words: a tag, &dbg and the entries of new_k, recycle_leaf and own for the x86-64 jit's inline fast paths (next commit).
* todo: overnight 5:27 queue verified; find_replace hardening notedGravatar zinc 13 days1-1/+4
| | | | | drop-check trees/sieve timings vs e67671d, reassignment and o3 drop/GC checks, plain new_k confirmation, and 1db57f7; freelist-inline still open.
* find_replace: cover o3 function prologues on every backendGravatar zinc 13 days7-7/+99
| | | | | | | | arm64, llvm and the region-interpreter rdrop path now watch the two prologue words the way the x86-64 jit already did, so icon.replace_function's lit+jmp patch retires a compiled callee (and clears fn_nat) instead of leaving a stale stub. three new icon regressions: repeated o3 replace, failed publication keeps the old entry, and a direct call after warming the region.
* todo: overnight prover/rcall/alloc statusGravatar zinc 13 days1-1/+1
|
* prover: do not restore length facts after a call-loopGravatar zinc 13 days3-17/+19
| | | | | | | Restoring undirtied lafacts when the body might free was wrong: push can grow an array without dirtying its name, so a[99] after push warned against a stale length 0. Keep the old lafact_keep rule; reorder explain_prover so the constant/affine cases run before the touch() loops.
* prover: len/cross-array/fixed-new/affine proofs; keep facts past call loopsGravatar zinc 13 days5-19/+44
| | | | | | | | Rebased the prover WIP onto main. lafact_keep restores undirtied allocation facts even when the loop body might free (so a later touch() no longer drops every length fact). proven_p uses ptr_still so an outer call keeps the check. entry_fact still supplies the size for the "might free" explain reason. bounds_prover.zc and explain_prover.zc land with test.sh coverage.
* wip: prover gaps (inline len bound, cross-array, rt.new depth, fixed new, ↵Gravatar zinc 13 days7-43/+172
| | | | affine i*n+k); unbuilt and untested
* o3: use new_k (size-class free lists) like plain codeGravatar zinc 13 days2-4/+7
| | | | | | | Constant-size typed new inside o3 now calls rt.new_k instead of always taking new_t/new_raw. new_k and recycle_leaf skip the o3 argument-fatten path the way free/recycle already do. trees o3 new/free on the x86-64 jit dropped from about 4.1 ms to about 2.7 ms per iter (matches plain).
* x86-64 o3: direct o3-to-o3 calls (rcall_x64 / rfinish_x64)Gravatar zinc 13 days2-16/+184
| | | | | | | | | Port arm64's rcall/rfinish to the x86-64 region jit: call the callee's entry stub through fn_nat with a built frame, return via linkstk, and fall back to o3_invoke when the stub is missing or the frame/depth check fails. Clear fn_nat on rforget and cover the function prologue so icon.replace_function drops the region (o3_caller_replace). vm_until saves jit_depth around nested bytecode, matching arm64.
* todo: destructors closed with what landed; overnight handoff notes (triage ↵Gravatar zinc 13 days1-1/+5
| | | | verdict, file and tsc installed, genome 0x70000)
* actor: a declared actor without its own drop gets one that awaits owed ↵Gravatar zinc 13 days7-7/+45
| | | | replies and closes the endpoint; the handler reaches the struct through endpoint.state so the struct isn't shared; spawn hint skips mailbox structs
* std: File, the first user of drops: std.Host.open(path, mode) returns an ↵Gravatar zinc 13 days5-6/+56
| | | | owned std.File (or null) with write and read, and its drop closes the descriptor; Host.writefile is built on it; file_drop.zc, learn and readme
* rt: gc_drops finalizes a droppable value that reaches itself (a cycle, or a ↵Gravatar zinc 13 days5-5/+42
| | | | drop capturing its own value), one per collection, each once; before, each waited for the other forever; spec 6.15.3, drop_gc_cycle.zc, drop_gc_self_capture.zc, design doc lists what landed
* o3: an o3 function called from normal code as a receiver method (run.method) ↵Gravatar zinc 13 days3-2/+17
| | | | enters and leaves the region and fattens its result, like a direct call; spec 4.10.3, o3_receiver_method_enter.zc
* o3: break and continue out of an o3 { } block call rt.o3_leave for each ↵Gravatar zinc 13 days4-1/+43
| | | | block they leave (the loop records the o3 depth it began at), so the depth returns to 0 and pending collections and drops run; spec 4.10.3, o3_break_continue_leave.zc
* rt: memreport marks a leaked value whose drop never ran with (drop); spec ↵Gravatar zinc 13 days4-3/+20
| | | | 4.11, readme, memdebug_report_drop.zc
* destructors: hint: x: has drop and is live at spawn; the worker's copy drops ↵Gravatar zinc 13 days5-1/+27
| | | | it too, on x.spawn() of a mailbox struct for each live owned local with a drop; spec 6.15.4, lsp hint check
* destructors: nothing moves out of a value with a drop: pop on an array with ↵Gravatar zinc 13 days7-1/+58
| | | | a drop, or on an array field of a value with a drop, is error: a: can't move out of a value with drop (fields were already borrowed projections); spec 6.15.5, four conformance programs
* destructors: reassigning an m owner that still holds a value frees the old ↵Gravatar zinc 13 days13-24/+100
| | | | value first, running its drop (right side first, then the free, then the store), with hint: x: reassigning frees the old value; a new value that is part of the old one is an error; u, d and captured owners keep the leak error; the new value's size, leaf type and drop are recorded like a declaration's; spec 6.8.5, 6.15.2
* genmap: default genome reservation 0x70000 words (the genome had 197 words ↵Gravatar zinc 13 days5-18/+18
| | | | left); the map constants in rt.zc and the README table move by 0x8000; gc.zc's reclaim bound is 900 (937 with the heap higher, 952 before) and the run-only section rewrites whatever its number
* merge work/triage: zc0typed.zc without .u on a typed parameter; a //:lines ↵Gravatar zinc 13 days5-10/+14
|\ | | | | | | marker ends unbounded;/unchecked; so self-hosted run-only images bounds-check the program again
| * compiler: a //:lines marker starts a new file, so unbounded; and unchecked; ↵Gravatar zinc 13 days4-9/+13
| | | | | | | | of the source before it end there: a program joined to the unbounded runtime in a self-hosted run-only image is bounds-checked again (since d55b5fd its index errors went unreported); runtime_image_test expects the trap's exit status 2; spec 4.15.1, 4.x unchecked, 5.15.3
| * tests: zc0typed.zc drops the .u on a typed parameter, which zc0 rejects ↵Gravatar zinc 13 days1-1/+1
|/ | | | since 45b53ef like the compiler (the typed/plain image check had compared an empty image)
* merge work/dtor: destructors (drop on any heap value, heap(), struct drop, ↵Gravatar zinc 13 days29-32/+841
|\ | | | | | | collector drops once with resurrection, freed blocks forget their drop)
| * todo: destructors item closed with what landed; what is left (reassignment ↵Gravatar zinc 13 days1-1/+2
| | | | | | | | free, no move out, spawn hint, memreport marker, o3 break/continue, droppable cycles, first users) is its own open item
| * test.sh: the small map's collector check rewrites gc.zc's reclaim bound ↵Gravatar zinc 13 days1-1/+1
| | | | | | | | whatever its number (it was 990 when the sed was written, gc.zc says 950 now, so the small map was held to the default map's count)
| * xref: baseline re-saved; the drop helpers (drop_attach, drop_member, ↵Gravatar zinc 13 days1-20/+76
| | | | | | | | drop_call, heap_box) write the expression state like other call helpers, and it also takes the 87 writers from earlier merges that main's baseline missed
| * compiler: the drop globals' comment says mailbox send, so nothing the ↵Gravatar zinc 13 days1-1/+1
| | | | | | | | compiler reads mentions actors (test.sh check)
| * docs: destructors: the free paths clear the entry in dropfree, right after ↵Gravatar zinc 13 days1-2/+2
| | | | | | | | the drop and before the children
| * rt: the free paths take one F_HASDROP test, and dropfree does the drop and ↵Gravatar zinc 13 days1-4/+4
| | | | | | | | the clearing out of line
| * destructors: heap(v), drop(v, f) / v.drop(f) / v.drop = f, struct drop ↵Gravatar zinc 13 days27-11/+589
| | | | | | | | methods, collector drops after the sweep (once, resurrection), freed blocks forget their drop, temporaries drop at statement end with a hint, actor send check; o3: no collection inside a region (pending until the outermost exit), no drops set or ended inside o3; spec 3.11.6, 4.10.3-4, 6.15
| * docs: destructors: clear drop entry and bits on free; planned reuse testGravatar zinc 13 days1-0/+5
| |
| * docs: destructors: value and type drops both run, side table storage, ↵Gravatar zinc 13 days1-9/+6
| | | | | | | | F_HASDROP/F_DROPPED bits
| * docs: revise destructors draft to acorn's rulings (drop on any heap value, ↵Gravatar zinc 13 days1-66/+117
| | | | | | | | heap() builtin, gc runs drops)
| * docs: draft design for destructors on heap objectsGravatar zinc 13 days1-0/+121
|/
* bench: sieve.zc and trees.zc take namespace and include rt, so run.py's ↵Gravatar zinc 13 days3-19/+22
| | | | checksums pass on main again (todo item closed)
* bench: baseline re-saved on main with the checks column and the rescaled ↵Gravatar zinc 13 days1-12/+12
| | | | arrays rows
* bench: a trap (zy exit 2) is labelled runtime trap with the stdout tail, ↵Gravatar zinc 13 days2-6/+9
| | | | since zy reports traps on stdout, in suite.py and bench.sh
* bench: matmul fill a = i % 7 - 2, b = i % 5 - 1 so its checksum is 63760 ↵Gravatar zinc 13 days2-2/+2
| | | | (checked against a python reference), not 0
* bench: a nonzero zy exit (1 compile error, 2 trap) or a wrong checksum fails ↵Gravatar zinc 13 days3-21/+73
| | | | the row with the stderr tail, in suite.py and bench.sh; selftest cases for exit 1, exit 2 and a wrong checksum. arrays rows scaled to ~3 ms a repetition (matmul 40x40, gather 98304 words); the baseline's arrays rows are stale until a re-save
* bench: baseline with arrays rows (checks column pending work/checks)Gravatar zinc 13 days1-10/+12
|
* bench: arrays rows, checks column from zy --explain-checks ('-' without it), ↵Gravatar zinc 13 days1-10/+68
| | | | bench-check fails when a row's check count changes; selftest cases
generated by cgit v1.2.3 (git 2.39.1) at 2026-10-27 17:26:58 +0000