Files
rea/experiments/atomic-codemode/sqlite-reference-question.txt
T
3aa685db39 feat(experiment): compose shallow outgoing references with explicit scope
Share one native parser for both directions, preserve occurrence identity and unknown function applicability, push kind filters to Kuna and reuse sources across fields/pages/scopes. Verify real SQLite machine references independently, including calls omitted from optimized IR and VM queries beyond graph capacity. Pin the aggregate model task before its paired runs.

Co-authored-by: gensokyo-dev <342580529+gensokyo-dev@users.noreply.github.com>
Co-authored-by: Kaoru0822 <208281322+kaoru0822-kitauji@users.noreply.github.com>
2026-10-16 08:48:24 +00:00

16 lines
992 B
Plaintext

Audit static call references in {{artifact_path}}, returning aggregate results
with focused supporting addresses and real Evidence references.
For sqlite3Fts3ExprParse, compare the native outgoing known-target call-reference
count with the retained recovered-IR call-operation count. Explain any difference
and verify the differing call against selected machine instructions; absence from
optimized IR must not be treated as absence from the executable.
For sqlite3VdbeExec, report the number of selected native known-target call-site
references, the number of distinct exact destination addresses, and the number
that target 0x296c0. Verify the call site at 0xf238b. This part concerns references
only: do not decompile the VM or return its instruction listing/source report.
Compose selected pages locally and return the requested aggregates rather than
all reference rows. State the limits for unresolved indirect calls, discovery,
and runtime symbol binding. Do not execute the target.