moon/zygotec - work-in-progress programming language.

	Commit message (Collapse)	Author	Age	Files	Lines
*	bounds: body scan, loop-entry hoisting, pointer proofs from requested size, ↵	zinc	13 days	1	-0/+3
\| \| \| \|	--explain-checks v1 (non-o3 code)
*	conformance and parity: a known entry that passes again is stale and fails ↵	zinc	13 days	1	-1/+2
\| \| \| \|	the run
*	x86-64 jit: inline enhancements (micro-ops lowered to registers, literal ↵	zinc	13 days	1	-0/+1
\| \| \| \|	specialization, ZYNOENH=1 to call xrun); enh_ops test; jit_x64_test in test.sh
*	bounds checking: port agent/bounds-checking onto main 0879d0a; unbounded ↵	zinc	13 days	1	-0/+3
\| \| \| \|	main in o3call, o3 tests expect no check, boundsrules, bounds_fixed, bounds_heap and zc0unbounded tests
*	parity: compare what zc0 and the self-hosted compiler print	zinc	13 days	1	-0/+15
	src/tools/parity.sh compiles each program of tests/programs, examples and examples/learn with zc0 (runtime, program, mkgenome, a microcore with the image embedded, kept under build/parity/) and runs it beside build/bin/zy < prog.zc, then compares stdout. what zc0 rejects is skipped and counted. tests/parity.known lists the differences that are by design (zc0 has no ownership analysis or memdebug checks). make parity runs it. tests/programs/parity_ops.zc pins operator precedence and associativity across every binary operator, unary operators, assignment and short-circuit order; its output matches a c compiler's.