D$: guarantee that no-alloc accesses are ordered even if aliased #2358
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
Currently, non-allocating accesses can be reordered with allocating accesses if they are to different virtual synonyms. Add hardware to detect and prevent this case. If there's no possibility of aliasing or non-allocating accesses, there's no additional HW cost. I'm not entirely happy with the approach (it adds a lot of fanout to what is sometimes a critical timing path, so at minimum it's leaky). Might revisit later.
girishpai
approved these changes
Mar 23, 2020
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.
Currently, non-allocating accesses can be reordered with allocating
accesses if they are to different virtual synonyms. Add hardware
to detect and prevent this case.
If there's no possibility of aliasing or non-allocating accesses,
there's no additional HW cost.
I'm not entirely happy with the approach (it adds a lot of fanout to
what is sometimes a critical timing path, so at minimum it's leaky).
Might revisit later.