-
Notifications
You must be signed in to change notification settings - Fork 61
Open
Labels
A-dereferenceableTopic: when exactly does a reference need to point to regular dereferenceable memory?Topic: when exactly does a reference need to point to regular dereferenceable memory?
Description
This question is intended to replace #33 and #265, and ask the general question of whether or not we can have a type, either user-defined or language-provided, that, when wrapped in a shared reference, guarantees that no accesses are introduced at the operational semantics level that are not part of the original program (and thus, if volatile accesses only are used, an implementation won't introduce any speculative reads).
If such a type can exist, the second question is what is the operational semantics of retagging as a shared reference to such a type.
schneiderfelipe, kupiakos and tylermasci16
Metadata
Metadata
Assignees
Labels
A-dereferenceableTopic: when exactly does a reference need to point to regular dereferenceable memory?Topic: when exactly does a reference need to point to regular dereferenceable memory?