Chandler Carruth 77b655c1c9 [PM] Don't require analysis results to be const in the new pass manager. ... I think this was just over-eagerness on my part. The analysis results need to often be non-const because they need to (in some cases at least) be updated by the transformation pass in order to remain correct. It also makes lazy analyses (a common case) needlessly annoying to write in order to make their entire state mutable. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@200881 91177308-0d34-0410-b5e6-96231b3b80d8		2014-02-05 21:41:42 +00:00
..
AttributesTest.cpp
CMakeLists.txt
ConstantsTest.cpp
DominatorTreeTest.cpp	[PM] Split DominatorTree into a concrete analysis result object which	2014-01-13 13:07:17 +00:00
InstructionsTest.cpp	Bug 18228 - Fix accepting bitcasts between vectors of pointers with a	2014-01-22 19:21:33 +00:00
IRBuilderTest.cpp
LegacyPassManagerTest.cpp
Makefile
MDBuilderTest.cpp
MetadataTest.cpp
PassManagerTest.cpp	[PM] Don't require analysis results to be const in the new pass manager.	2014-02-05 21:41:42 +00:00
PatternMatch.cpp
TypeBuilderTest.cpp
TypesTest.cpp
ValueMapTest.cpp
ValueTest.cpp
VerifierTest.cpp	[PM] Make the verifier work independently of any pass manager.	2014-01-19 02:22:18 +00:00
WaymarkTest.cpp