<feed xmlns='http://www.w3.org/2005/Atom'>
<title>ida-tui.git/.auto/parked/fast_pc_nums.patch, branch pre-codemode</title>
<subtitle>tui for headless ida</subtitle>
<id>https://git.sl0p.foo/ida-tui.git/atom/.auto/parked/fast_pc_nums.patch?h=pre-codemode</id>
<link rel='self' href='https://git.sl0p.foo/ida-tui.git/atom/.auto/parked/fast_pc_nums.patch?h=pre-codemode'/>
<link rel='alternate' type='text/html' href='https://git.sl0p.foo/ida-tui.git/'/>
<updated>2026-08-07T07:13:33Z</updated>
<entry>
<title>Park two proven-but-unresolvable F5-path optimisations, and record how to spot a counter-drift outlier</title>
<updated>2026-08-07T07:13:33Z</updated>
<author>
<name>user</name>
<email>user@clank</email>
</author>
<published>2026-08-07T07:13:33Z</published>
<link rel='alternate' type='text/html' href='https://git.sl0p.foo/ida-tui.git/commit/?id=0fc0b3a9d667f7f464939bce8bfdf4cd9cd889bb'/>
<id>urn:sha1:0fc0b3a9d667f7f464939bce8bfdf4cd9cd889bb</id>
<content type='text'>
pc_nums allocated three ctree_item_t SWIG objects per candidate column -- the
third instance of the same fault already fixed in decomp_map and found in
decompile_function_safe. 1247 -&gt; 614ms warm over 18991 lines of bash, identical
literal counts, 0 mismatches over echo's 128 functions.

Both it and the fast decompile_function_safe are parked rather than applied:
together they are worth ~350ms against a run-to-run spread of ~500ms on this
box (means 25045 with, 25140 without over seven runs), so the benchmark cannot
resolve them. Neither adds complexity -- both remove allocations -- so they are
kept on disk with their measurements for a per-operation-latency goal.

Also records the 27283ms outlier: the work counters moved with it, which is how
an outlier is told from a regression.
</content>
</entry>
</feed>
