Paul Robinson c3e82bf9f5 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. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@221168 91177308-0d34-0410-b5e6-96231b3b80d8		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
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