forked from OSchip/llvm-project
edf5996b06
analysis passes, support pre-registering analyses, and use that to implement parsing and pre-registering a custom alias analysis pipeline. With this its possible to configure the particular alias analysis pipeline used by the AAManager from the commandline of opt. I've updated the test to show this effectively in use to build a pipeline including basic-aa as part of it. My big question for reviewers are around the APIs that are used to expose this functionality. Are folks happy with pass-by-lambda to do pass registration? Are folks happy with pre-registering analyses as a way to inject customized instances of an analysis while still using the registry for the general case? Other thoughts of course welcome. The next round of patches will be to add the rest of the alias analyses into the new pass manager and wire them up here so that they can be used from opt. This will require extending the (somewhate limited) functionality of AAManager w.r.t. module passes. Differential Revision: http://reviews.llvm.org/D17259 llvm-svn: 261197 |
||
|---|---|---|
| .. | ||
| AsmWriterTest.cpp | ||
| AttributesTest.cpp | ||
| CMakeLists.txt | ||
| ConstantRangeTest.cpp | ||
| ConstantsTest.cpp | ||
| DebugInfoTest.cpp | ||
| DominatorTreeTest.cpp | ||
| IRBuilderTest.cpp | ||
| InstructionsTest.cpp | ||
| IntrinsicsTest.cpp | ||
| LegacyPassManagerTest.cpp | ||
| MDBuilderTest.cpp | ||
| MetadataTest.cpp | ||
| PassManagerTest.cpp | ||
| PatternMatch.cpp | ||
| TypeBuilderTest.cpp | ||
| TypesTest.cpp | ||
| UseTest.cpp | ||
| UserTest.cpp | ||
| ValueHandleTest.cpp | ||
| ValueMapTest.cpp | ||
| ValueTest.cpp | ||
| VerifierTest.cpp | ||
| WaymarkTest.cpp | ||