This is an archive of the discontinued LLVM Phabricator instance.

[LAA-memchecks 1/3] Split out NumComparisons checks. NFC
ClosedPublic

Authored by anemet on Mar 6 2015, 1:21 PM.

Details

Summary

The check for the number of memchecks will be moved to the client of
this analysis. Besides allowing for transform-specific thresholds, this
also lets Loop Distribution post-process the memchecks; Loop
Distribution only needs memchecks between pointers of different
partitions.

The motivation for this first patch is to untangle the CanDoRT check
from the NumComparison check before moving the NumComparison part.
CanDoRT means that we couldn't determine the bounds for the pointer.
Note that NumComparison is set independent of this flag.

Diff Detail

Event Timeline

anemet updated this revision to Diff 21388.Mar 6 2015, 1:21 PM
anemet retitled this revision from to [LAA-memchecks 1/3] Split out NumComparisons checks. NFC.
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.Mar 7 2015, 11:01 PM
hfinkel edited edge metadata.

LGTM.

lib/Analysis/LoopAccessAnalysis.cpp
1083

I know you did not change the terminology here, but I'm not quite sure what 'unsizable pointer' means. Could we say 'unknown dependence' or 'unknown bounds'?

1127

Same comment here about 'unsizable pointer'

This revision is now accepted and ready to land.Mar 7 2015, 11:01 PM
anemet added inline comments.Mar 9 2015, 12:18 PM
lib/Analysis/LoopAccessAnalysis.cpp
1083

Sure, I think 'unknown bounds' is better.

Thanks very much for the reviews!

anemet closed this revision.Mar 10 2015, 12:16 PM

r231816 and r231821 (for the comment improvement).

Thanks, Hal!