diff options
author | Andrew Trick <atrick@apple.com> | 2012-06-26 04:11:38 +0000 |
---|---|---|
committer | Andrew Trick <atrick@apple.com> | 2012-06-26 04:11:38 +0000 |
commit | fb2ba3e1cbcb4a4374fda393fe3f1462714bd614 (patch) | |
tree | 8eed88117820342729009289bcc1fee316229c51 /llvm/lib/CodeGen/MachineBlockPlacement.cpp | |
parent | fecf9379383e43457047fb6d5ef497a63ba486e0 (diff) | |
download | llvm-fb2ba3e1cbcb4a4374fda393fe3f1462714bd614.zip llvm-fb2ba3e1cbcb4a4374fda393fe3f1462714bd614.tar.gz llvm-fb2ba3e1cbcb4a4374fda393fe3f1462714bd614.tar.bz2 |
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.
llvm-svn: 159183
Diffstat (limited to 'llvm/lib/CodeGen/MachineBlockPlacement.cpp')
0 files changed, 0 insertions, 0 deletions