<feed xmlns='http://www.w3.org/2005/Atom'>
<title>pure/docs/research/133-register-tiles-measured.md, branch master</title>
<subtitle>Verified execution runtime unifying state, persistence, and replication.
</subtitle>
<id>http://git.yeowoo.org/pure/atom?h=master</id>
<link rel='self' href='http://git.yeowoo.org/pure/atom?h=master'/>
<link rel='alternate' type='text/html' href='http://git.yeowoo.org/pure/'/>
<updated>2026-10-08T13:36:27Z</updated>
<entry>
<title>Research 132 and 133 corrected: the per-batch cost was icount's three rounds over one round's batches, 3x too high; about 2,300 instructions (0.33 us) in a small block, 0.90 us in knapsack's (38% of its time, not 20%)</title>
<updated>2026-10-08T13:36:27Z</updated>
<author>
<name>eunhhu</name>
<email>necpition205@gmail.com</email>
</author>
<published>2026-10-08T13:36:27Z</published>
<link rel='alternate' type='text/html' href='http://git.yeowoo.org/pure/commit/?id=3e3f008b942106cedb59ebca760376274c2fcb84'/>
<id>urn:sha1:3e3f008b942106cedb59ebca760376274c2fcb84</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Research 133: register tiles measured (132's deciding experiment): past the bar on roots (0.71x the compiled code's cycles a step), not on knapsack (4x) or BFS (2.4x), as NEON has no gather and a tile's lanes go out and in one by one; tight passes of the batch executor's own shape in the same run at 1.2x (BFS) and 0.4x (knapsack, clang): the shape is right and the 3x is implementation, so 132's A (a batch program made once at load, loops tight by type, width and stride, fewer passes) is the way; tiles kept aside for chains of arithmetic; 132, 024 and CHECKPOINT say so</title>
<updated>2026-10-08T12:39:18Z</updated>
<author>
<name>eunhhu</name>
<email>necpition205@gmail.com</email>
</author>
<published>2026-10-08T12:39:18Z</published>
<link rel='alternate' type='text/html' href='http://git.yeowoo.org/pure/commit/?id=66e3f7d2adbc752b1e7a6c052675868a564314d4'/>
<id>urn:sha1:66e3f7d2adbc752b1e7a6c052675868a564314d4</id>
<content type='text'>
</content>
</entry>
</feed>
