[Fix][Arith] Isolate Z3 contexts and make memoization deterministic - #20097
Merged
Conversation
MasterJH5574
approved these changes
Aug 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
2 participants
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.
This PR improves the reliability and determinism of the Z3 arithmetic prover by introducing scoped Z3 contexts, safely preserving context ownership when cloning analyzers, and replacing unordered-map-owned Z3 expressions with a deterministic memo pool and reusable slots. It prevents Z3 AST allocation history and hash iteration order from affecting
CanProveresults under resource limits, while adding regression coverage for context lifetime, memo cleanup, slot reuse, and analyzer cloning.Related TileLang-side changes: tile-ai#58 & tile-ai#62.