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
{{ message }}
This repository was archived by the owner on Apr 28, 2023. It is now read-only.
memory promotion: check for any reuse within outer schedule
The original code checks for reuse by applying a "full schedule"
to the domain of the access relation and then checking if
there is more than one instance of this full schedule accessing
a group element for fixed values of some outer part of this
full schedule, where fixing these values is performed separately
for each statement.
The new code is much simpler and directly checks for multiple
statement instances accessing an element within an outer schedule.
Note that because of the way the "full schedule" is constructed,
some statement instances may get mapped to the same full schedule
instance and could therefore project out some reuse.
The new code may therefore detect some reuse where the old code did not.
Detecting more reuse is not the purpose of this commit,
but the new form of detection does make it easier to understand
which situation are considered to constitute reuse.
0 commit comments