forked from OSchip/llvm-project
2e02d560aa
The previously implemented approach is to follow value definitions and
create write accesses ("push defs") while searching for uses. This
requires the same relatively validity- and requirement conditions to be
replicated at multiple locations (PHI instructions, other instructions,
uses by PHIs).
We replace this by iterating over the uses in a SCoP ("pull in
requirements"), and add writes only when at least one read has been
added. It turns out to be simpler code because each use is only iterated
over once and writes are added for the first access that reads it. We
need another iteration to identify escaping values (uses not in the
SCoP), which also makes the difference between such accesses more
obvious. As a side-effect, the order of scalar MemoryAccess can change.
Differential Revision: http://reviews.llvm.org/D15706
llvm-svn: 259987
|
||
|---|---|---|
| .. | ||
| GICHelper.cpp | ||
| RegisterPasses.cpp | ||
| SCEVAffinator.cpp | ||
| SCEVValidator.cpp | ||
| ScopHelper.cpp | ||
| ScopLocation.cpp | ||