C++: Fix join order problem in TaintedAllocationSize.#18578
Merged
jketema merged 1 commit intogithub:mainfrom Jan 23, 2025
Merged
C++: Fix join order problem in TaintedAllocationSize.#18578jketema merged 1 commit intogithub:mainfrom
jketema merged 1 commit intogithub:mainfrom
Conversation
Contributor
There was a problem hiding this comment.
Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.
Tip: Copilot code review supports C#, Go, Java, JavaScript, Markdown, Python, Ruby and TypeScript, with more languages coming soon. Learn more
Contributor
Author
|
And here's the RA with tuple counts to compare. |
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.
Alternative to #18564. Hopefully this should be a much better join-order: This reorders the two
readsVariableconjuncts pushing one into the offending predicate and pulling the other out. The result isvariableEqualityCheckedInBlock(Variable checkedVar, IRBlock bb)which appears to have a good column correlation (i.e. small size), and it's simple enough to handle the inlinedensuresEq. This makes sense since its semantic interpretation also seems like a reasonable thing to materialise. The subsequent join is fast when it happens on both columns, which we ensure by adding the basic block as an additional column toreadsVariable(it's functional so should be a safe addition).