Paul Robinson 2b27bd26b6 Normally an 'optnone' function goes through fast-isel, which does not ... call DAGCombiner. But we ran into a case (on Windows) where the calling convention causes argument lowering to bail out of fast-isel, and we end up in CodeGenAndEmitDAG() which does run DAGCombiner. So, we need to make DAGCombiner check for 'optnone' after all. Commit includes the test that found this, plus another one that got missed in the original optnone work. llvm-svn: 221168		2014-11-03 18:19:26 +00:00
..
2008-09-03-Mutual.ll
2008-09-03-ReadNone.ll
2008-09-03-ReadOnly.ll
2008-09-13-VolatileRead.ll
2008-12-29-Constant.ll
2009-01-02-LocalStores.ll
2009-01-04-Annotate.ll
2010-10-30-volatile.ll
annotate-1.ll
atomic.ll
nocapture.ll	When analyzing params/args for readnone/readonly, don't forget to consider that a pointer argument may be passed through a callsite to the return, and that we may need to analyze it. Fixes a bug reported on llvm-dev: http://lists.cs.uiuc.edu/pipermail/llvmdev/2014-May/073098.html	2014-05-30 02:31:27 +00:00
noreturn.ll
optnone-simple.ll	Normally an 'optnone' function goes through fast-isel, which does not	2014-11-03 18:19:26 +00:00
optnone.ll	[optnone] Make the optnone attribute effective at suppressing function	2014-08-13 10:49:33 +00:00
readattrs.ll	When analyzing params/args for readnone/readonly, don't forget to consider that a pointer argument may be passed through a callsite to the return, and that we may need to analyze it. Fixes a bug reported on llvm-dev: http://lists.cs.uiuc.edu/pipermail/llvmdev/2014-May/073098.html	2014-05-30 02:31:27 +00:00