Chandler Carruth edc84248f8 [PM] The order of evaluation of these analyses is actually significant, ... much to my horror, so use variables to fix it in place. This terrifies me. Both basic-aa and memdep will provide more precise information when the domtree and/or the loop info is available. Because of this, if your pass (like GVN) requires domtree, and then queries memdep or basic-aa, it will get more precise results. If it does this in the other order, it gets less precise results. All of the ideas I have for fixing this are, essentially, terrible. Here I've just caused us to stop having unspecified behavior as different implementations evaluate the order of these arguments differently. I'm actually rather glad that they do, or the fragility of memdep and basic-aa would have gone on unnoticed. I've left comments so we don't immediately break this again. This should fix bots whose host compilers evaluate the order of arguments differently from Clang. llvm-svn: 263231		2016-03-11 13:26:47 +00:00
..
Hello	Remove autoconf support	2016-01-26 21:29:08 +00:00
InstCombine	[PM] Make the AnalysisManager parameter to run methods a reference.	2016-03-11 11:05:24 +00:00
Instrumentation	Remove llvm::getDISubprogram in favor of Function::getSubprogram	2016-03-11 02:14:16 +00:00
IPO	[PM] Make the AnalysisManager parameter to run methods a reference.	2016-03-11 11:05:24 +00:00
ObjCARC	ADT: Remove == and != comparisons between ilist iterators and pointers	2016-02-21 20:39:50 +00:00
Scalar	[PM] The order of evaluation of these analyses is actually significant,	2016-03-11 13:26:47 +00:00
Utils	Remove llvm::getDISubprogram in favor of Function::getSubprogram	2016-03-11 02:14:16 +00:00
Vectorize	[SLP] Add -slp-min-reg-size command line option.	2016-03-10 02:49:47 +00:00
CMakeLists.txt
LLVMBuild.txt