Closed BiwefC closed 3 weeks ago
MXR never affects store instructions. It makes executable pages readable, not writable. Pointer masking isn't going to change that.
MXR never affects store instructions. It makes executable pages readable, not writable. Pointer masking isn't going to change that.
But in Spike implementation, pmm directly masked by MXR, regardless of the instruction type. Does this means that there is an issue in Spike's implementation?
I think the implication is that yes, MXR affects pointer masking for both both loads and stores, but it doesn't really matter because there's no known use case for doing stores with MXR enabled (execute-only pages aren't writable).
Spike is following the spec.
I agree with @SiFiveHolland. I think there is nothing in the spec that says it doesn't apply to stores, but it does not matter.
In pointer-masking v1.0.0-rc2, MXR will effect whether pointer masking is applied or not. But should store instructions is applied with pointer masking be affected by MXR? If so, why should they be affected?