Repository navigation
Recognize evidenced STL, ATL and libc operations across source views - #537
Merged
Merged
Conversation
NeverSightAI
marked this pull request as ready for review
October 5, 2026 13:45
This was referenced Oct 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Recognizes supported standalone and inlined STL/ATL operations so function lists, call sites and decompiled views can show readable library identities with traceable evidence. Five compiler-backed profiles cover 59 libc++, MSVC STL, shared ATL/MFC string, COM and musl rules. Bounded MedIR matching and existing byte signatures require consistent identity/layout/dataflow evidence; ambiguous matches and custom lookalikes remain unchanged.
The shared session identity preserves user/stated names and raw linkage while providing qualified display names. HighC and LLVMC record precise original occurrences, including PDB member projections, and authorize a fold only when the annotated render reproduces ordinary C byte for byte. Desktop folds are reversible; copy and export retain complete source. CLI JSON and worker pages expose the same identities and evidence. A call remains a statement when LLVMC projects its return to void, preserving its effects.
Feature data is in merged signatures #16. This PR pins the unchanged data plus the consumer receipt in signatures #17. The receipt records the tested engine revision, exact coverage and limitations; rule verification flags remain pending separate review.
Validation on macOS arm64 Release with the NeverD LLVM r3 toolchain:
The full aggregate is not green. The integrated run executed 15,572 CTest entries with 113 failures. Lower-concurrency replay and a separate build of dev
c32e0a31creproduced 88 distinct failures on both revisions. Two newly exposed JSON-parser test failures were fixed and passed; a Swift compiler timeout passed on retry. The machine-readable receipt lists the baseline failures. Existing dev benchmark reports also fail the repository-wide private-path check; this PR's changed files pass separately.CPU/driver emulation, Unicorn semantic tests and the external binary corpus were disabled. MSVC PDB views retain their existing external record-type requirements; no self-contained STL recompilation is claimed. ATL fixtures are analysis-only and do not authorize native exception rewriting. The shared-tail musl memmove body retains recognition but remains unfolded. The full signatures Python suite has 7 existing macOS collector/tool compatibility errors among 173 tests, separate from the passing feature tests.
Closes #495.