[control] separate fence and fence.i instructions #1149
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
for read-only caches: send fence/synchronization before reloading. for read-write caches: send fence/synchronization after flushing but before reloading
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.
Previously, the commands
fenceandfence.iwere functionally equivalent. The execution of one of the two instructions leads to a complete cache re-synchronization (flushing/clearing/reloading the instruction and data cache). However, this is too inefficient, so this PR splits the two commands functionally.fence.i- clear and reload instruction cachefence- flush, clear and reload data cacheAfter the L1 caches, both instructions still behave identically.