[herd] Compute EX and X sets in OCaml#1894
Closed
maranget wants to merge 4 commits into
Closed
Conversation
The predicate now identifies *all* memory events generated by AMO instructions --- before, it was identifying memory stores. Also notice that `is_amo` is now significant for all architextures, while it was used only for RISCV previously.
We compute non-explicit atomic pairs as the restriction of `iico_data` from non-explict atomic reads to non-explicit atomic writes. We here rely on the assumption that *all* atonic pairs of non-explicit accesses result from page table updates. As for explicit accesses, we compute AMO's and exclusives differently. + AMO -> The read and the write are generated by the same instrction + Exclusives -> No exclusive in-between.
Authored-by: Hadrien Renaud <Hadrien.Renaud2@arm.com>
Member
Author
|
Superseded by PR #1908. |
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
2 participants
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.
Here for reference and comparison with PR #1889. Not meant to be merged.