C++: Protect the value numbering library from instructions with multiple enclosing functions #20369
+222
−237
Conversation
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
… The next commits will protect the recursion from instructions which has multiple IRFunctions and assign such instructions a unique value number so it won't make sense for them to have an IRFunction column.
…n instructions with a non-unique IRFUnction a unique value number.
There was a problem hiding this comment.
Pull Request Overview
This PR addresses a performance issue in the value numbering library caused by instructions with multiple enclosing IR functions. The fix ensures that such instructions are assigned unique value numbers to prevent tuple count explosion in downstream analysis.
- Modifies the value numbering system to handle instructions with multiple enclosing functions
- Adds filtering logic to detect problematic instructions with multiple enclosing functions
- Changes unique value number generation to be instruction-based rather than function-based
.../lib/semmle/code/cpp/ir/implementation/unaliased_ssa/gvn/internal/ValueNumberingInternal.qll
Show resolved
Hide resolved
.../lib/semmle/code/cpp/ir/implementation/unaliased_ssa/gvn/internal/ValueNumberingInternal.qll
Show resolved
Hide resolved
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.
We hit a performance problem on https://github.com/openvinotoolkit/oneDNN in the 2.23.0 release, and after looking long and hard at the resulting tuple count explosion in the
IRGuardslibrary I narrowed the problem down to a fewInitializeParameterinstructions with more than one enclosing IR functions.Since each value number has an
IRFunctioncolumn this meant that theseInitializeParameterinstructions mapped to many many value numbers which meant that certain joins inIRGuardwhich were expected to have no fan-out caused a large explosion.Ideally, we should have no instruction with multiple enclosing
IRFunctions. However, to mitigate this problem going forward this PR ensures that instructions with multipleIRFunctions are assigned a unique value number.Commit-by-commit review recommended.