Bill Wendling 84b6706d90 Omit extracting a loop if one of the exits is a landing pad. ...

The landing pad must accompany the invoke when it's extracted. However, if it
does, then the loop isn't properly extracted. I.e., the resulting extraction has
a loop in it. The extracted function is then extracted, etc. resulting in an
infinite loop.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@140193 91177308-0d34-0410-b5e6-96231b3b80d8

2011-09-20 22:23:09 +00:00

..

ArgumentPromotion.cpp

…

CMakeLists.txt

…

ConstantMerge.cpp

…

DeadArgumentElimination.cpp

…

ExtractGV.cpp

…

FunctionAttrs.cpp

Revert a bit of r137667; the logic in question can safely handle atomic load/store.

2011-08-16 01:28:22 +00:00

GlobalDCE.cpp

…

GlobalOpt.cpp

Minor comment fixes.

2011-08-16 00:20:11 +00:00

InlineAlways.cpp

…

Inliner.cpp

…

InlineSimple.cpp

…

Internalize.cpp

…

IPConstantPropagation.cpp

…

IPO.cpp

C API functions must be able to see their extern "C" definitions, or it will be impossible to call them from C.

2011-08-19 01:36:54 +00:00

LoopExtractor.cpp

Omit extracting a loop if one of the exits is a landing pad.

2011-09-20 22:23:09 +00:00

Makefile

…

MergeFunctions.cpp

…

PartialInlining.cpp

…

PassManagerBuilder.cpp

Add a mechanism for optimisation plugins to register passes that all front ends can use without needing to be aware of the plugin (or the plugin be aware of the front end).

2011-08-16 13:58:41 +00:00

PruneEH.cpp

…

StripDeadPrototypes.cpp

…

StripSymbols.cpp

…