Adam Nemet 9449a00cc1 [BPI] Add new LazyBPI analysis ... Summary: The motivation is the same as in D22141: In order to add the hotness attribute to optimization remarks we need BFI to be available in all passes that emit optimization remarks. BFI depends on BPI so unless we make this lazy as well we would still compute BPI unconditionally. The solution is to use the new LazyBPI pass in LazyBFI and only compute BPI when computation of BFI is requested by the client. I extended the laziness test using a LoopDistribute test to also cover BPI. Reviewers: hfinkel, davidxl Subscribers: llvm-commits Differential Revision: https://reviews.llvm.org/D22835 llvm-svn: 277083		2016-07-28 23:31:12 +00:00
..
basic-with-memchecks.ll
basic.ll
bounds-expansion-bug.ll
crash-in-memcheck-generation.ll
diagnostics-with-hotness-lazy-BFI.ll	[BPI] Add new LazyBPI analysis	2016-07-28 23:31:12 +00:00
diagnostics-with-hotness.ll	[OptDiag,LDist] Convert remaining opt remarks to use the new API	2016-07-21 21:21:34 +00:00
diagnostics.ll	[LoopDist] Fix typo in diagnostic	2016-07-14 22:33:46 +00:00
metadata.ll	[LoopDist] Add llvm.loop.distribute.enable loop metadata	2016-04-27 05:28:18 +00:00
no-if-convert.ll
outside-use.ll
pr28443.ll	[LoopAccessAnalysis] Fix an integer overflow	2016-07-07 06:24:36 +00:00
program-order.ll
symbolic-stride.ll	[LAA] Enable symbolic stride speculation for all LAA clients	2016-06-17 22:35:41 +00:00
unknown-bounds-for-memchecks.ll