Revert isIndexableDataAddrPresent to UDATA #20934
Merged
Conversation
This file contains 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
Since #20819 did not resolved perf regression, and introduced DDR incompatibility since the last release/split, isIndexableDataAddrPresent is reverted back to type UDATA that was the type at the last split. Performance regression will be dealt later in a separate change. Signed-off-by: Aleksandar Micic <[email protected]>
|
@dmitripivkine @keithc-ca please review |
dmitripivkine
approved these changes
Jan 14, 2025
keithc-ca
approved these changes
Jan 14, 2025
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.
Since #20819 did not resolved perf regression, and introduced DDR incompatibility since the last release/split, isIndexableDataAddrPresent is reverted back to type UDATA that was the type at the last split.
Performance regression will be dealt later in a separate change.