Tom Stellard 857550322c StructurizeCFG: Use LoopInfo analysis for better loop detection ...

We were assuming that each back-edge in a region represented a unique
loop, which is not always the case.  We need to use LoopInfo to
correctly determine which back-edges are loops.

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

2014-12-03 04:28:32 +00:00

..

Hello

[CMake] Add LLVM_LINK_COMPONENTS to loadable modules, LLVMHello and BugpointPasses, on Win32.

2014-07-13 13:36:48 +00:00

InstCombine

[Statepoints 3/4] Statepoint infrastructure for garbage collection: SelectionDAGBuilder

2014-12-02 18:50:36 +00:00

Instrumentation

Emit the entry block first and the exit block second, then all the blocks in between afterwards. This is what gcc always does, and some out of tree tools depend on that.

2014-12-03 02:45:01 +00:00

IPO

Prologue support

2014-12-03 02:08:38 +00:00

ObjCARC

Update SetVector to rely on the underlying set's insert to return a pair<iterator, bool>

2014-11-19 07:49:26 +00:00

Scalar

StructurizeCFG: Use LoopInfo analysis for better loop detection

2014-12-03 04:28:32 +00:00

Utils

[SwitchLowering] Handle destinations on multiple phi instructions

2014-12-02 18:31:53 +00:00

Vectorize

PR21302. Vectorize only bottom-tested loops.

2014-12-02 22:59:06 +00:00

CMakeLists.txt

…

LLVMBuild.txt

…

Makefile

…