Release v0.23.0: CoreTrace needs the ownership summary speed-up of #187 #227

CoreTrace pins the stack analyzer at v0.22.0, which takes 30 minutes to analyze CoreTrace's own code in an unoptimized build; main takes 5 (CoreTrace/coretrace#169). No release contains the change yet: v0.22.0 (2026-09-25) is still the latest, and main is 150 commits ahead.

Measured

ctrace --compile-commands <CoreTrace's 22 translation units> --invoke ctrace_stack_analyzer, on Linux x86_64 with LLVM 20.1.2, a fresh cache, and one run at a time:

The gain comes from #187, measured in Release under the same conditions at four commits:

Between v0.22.0 and c1e60b8, the analysis got slower (3 min 16 s to 7 min 12 s in Release); #187 more than makes up for it. A release cut before #187 would have been slower than v0.22.0.

With main, CoreTrace's ctest (77 tests) and its F7 harness pass, and its bridge builds unchanged.

To do

• Release v0.23.0 from main (0668fb8 or later, with CI green).

Then, in CoreTrace (CoreTrace/coretrace#169)

• Pin GIT_TAG v0.23.0 in cmake/stackUsageAnalyzer.cmake. The branch build/169-update-stack-analyzer already pins 0668fb8.
• Build with the tag and run ctest.
• Open the pull request (build(deps): update coretrace-stack-analyzer to v0.23.0, closing docs: cross-TU function facts design and implementation plan #169), and check that CI passes on Linux and macOS: the measurements above are Linux only.