This is an archive of the discontinued LLVM Phabricator instance.

[LoopAccesses] Stash the report from the analysis rather than emitting it
ClosedPublic

Authored by anemet on Feb 16 2015, 2:19 PM.

Details

Summary

The transformation passes will query this and then emit them as part of
their own report. The currently only user LV is modified to do just
that.

This is part of the patchset that converts LoopAccessAnalysis into an
actual analysis pass.

Diff Detail

Event Timeline

anemet updated this revision to Diff 20050.Feb 16 2015, 2:19 PM
anemet retitled this revision from to [LoopAccesses] Stash the report from the analysis rather than emitting it.
anemet updated this object.
anemet edited the test plan for this revision. (Show Details)
anemet added reviewers: hfinkel, aschwaighofer, nadav.
anemet added a subscriber: Unknown Object (MLST).
hfinkel accepted this revision.Feb 16 2015, 4:21 PM
hfinkel edited edge metadata.

I imagine that, in the future, we might generate multiple report messages. I think that this is fine for now, however. LGTM.

lib/Analysis/LoopAccessAnalysis.cpp
1080

report -> reports

This revision is now accepted and ready to land.Feb 16 2015, 4:21 PM

I imagine that, in the future, we might generate multiple report messages. I think that this is fine for now, however. LGTM.

Yeah, initially I wrote this with a SmallVector. When later in the patchset I was writing the part to prepend "loop cannot be vectorized" to the report for the vectorizer I realized that there was no point making that a loop, etc since we only have reports with a single message in them.

anemet closed this revision.Mar 1 2015, 9:38 PM

229891