You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AFAIK, both these entries specify the priority for mcontrol/mcontrol6 load data before (the second one explitly, the first one as one of the options).
Is this a typo? If not, what is the priority for mcontrol/mcontrol6 load data before?
The text was updated successfully, but these errors were encountered:
Yes, this is not accurately specified. It has the lowest priority and shouldn't be included with the rest of them in the middle of that table.
Load/store address and store data are known before doing any memory access. Therefore, they can have a relatively high priority (which is the first thing you show). Load data cannot possibly be known until the load has been performed. That must happen after address translation and PMP checks. So load data before must have the lowest priority.
Nobody probably caught this because load data should (but not must) fire after instead of before. See table 11.
There are two entries in table 10 (5.3. Priority)
and
AFAIK, both these entries specify the priority for
mcontrol/mcontrol6 load data before
(the second one explitly, the first one as one of the options).Is this a typo? If not, what is the priority for
mcontrol/mcontrol6 load data before
?The text was updated successfully, but these errors were encountered: