summaryrefslogtreecommitdiff
path: root/test/MC/X86/x86-32-avx.s
diff options
context:
space:
mode:
authorAndrew Trick <atrick@apple.com>2012-06-26 04:11:38 +0000
committerAndrew Trick <atrick@apple.com>2012-06-26 04:11:38 +0000
commitc9b1e25493b393013b28e5d457f2fb2845a4dd9f (patch)
treec1193bd83841e829e703beeb00c1fe6415de5f05 /test/MC/X86/x86-32-avx.s
parent5ac3f96c0e4a1f6b8253aabf74fe30b0439e9bdf (diff)
downloadllvm-c9b1e25493b393013b28e5d457f2fb2845a4dd9f.tar.gz
llvm-c9b1e25493b393013b28e5d457f2fb2845a4dd9f.tar.bz2
llvm-c9b1e25493b393013b28e5d457f2fb2845a4dd9f.tar.xz
Enable the new LoopInfo algorithm by default.
The primary advantage is that loop optimizations will be applied in a stable order. This helps debugging and unit test creation. It is also a better overall implementation without pathologically bad performance on deep functions. On large functions (llvm-stress --size=200000 | opt -loops) Before: 0.1263s After: 0.0225s On deep functions (after tweaking llvm-stress, thanks Nadav): Before: 0.2281s After: 0.0227s See r158790 for more comments. The loop tree is now consistently generated in forward order, but loop passes are applied in reverse order over the program. If we have a loop optimization that prefers forward order, that can easily be achieved by adding a different type of LoopPassManager. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@159183 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'test/MC/X86/x86-32-avx.s')
0 files changed, 0 insertions, 0 deletions