Arthur Eubanks
34de63c37f
[test] Remove unnecessary require<> in LoopAccessAnalysis tests
...
These function analyses are always available in loop passes.
2022-02-04 18:03:55 -08:00
Arthur Eubanks
50153213c8
[test][NewPM] Remove RUN lines using -analyze
...
Only tests in llvm/test/Analysis.
-analyze is legacy PM-specific.
This only touches files with `-passes`.
I looked through everything and made sure that everything had a new PM equivalent.
Reviewed By: MaskRay
Differential Revision: https://reviews.llvm.org/D109040
2021-09-02 11:38:14 -07:00
Arthur Eubanks
54e1bf1154
[LoopAccessAnalysis][NewPM] Fix tests to work under NPM
...
Pin RUN lines with -analyze to legacy PM, add corresponding NPM RUN lines.
Reviewed By: fhahn
Differential Revision: https://reviews.llvm.org/D87662
2020-09-15 11:06:47 -07:00
Sean Silva
284b0324e2
[PM] Avoid getResult on a higher level in LoopAccessAnalysis
...
Note that require<domtree> and require<loops> aren't needed because they
come in implicitly via the loop pass manager.
llvm-svn: 274712
2016-07-07 01:01:53 +00:00
Xinliang David Li
8a021317a2
[PM] Port LoopAccessInfo analysis to new PM
...
It is implemented as a LoopAnalysis pass as
discussed and agreed upon.
llvm-svn: 274452
2016-07-02 21:18:40 +00:00
Adam Nemet
c62e554e9a
[LAA] Include MaxSafeDepDistBytes in the analysis print-out
...
llvm-svn: 269508
2016-05-13 22:49:13 +00:00