llvm/test/Transforms/LoopUnswitch, branch release_32http://llvm.orghttps://git.amat.us/llvm/atom/test/Transforms/LoopUnswitch?h=release_322012-09-26T09:51:39ZFix tests that didn't test anything.2012-09-26T09:51:39ZBenjamin Kramerbenny.kra@googlemail.com2012-09-26T09:51:39Zurn:sha1:e7381cc99c3d5a579dd039f0d8e1b930f5735684
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@164686 91177308-0d34-0410-b5e6-96231b3b80d8
Convert the uses of '|&' to use '2>&1 |' instead, which works on old2012-07-02T18:37:59ZChandler Carruthchandlerc@gmail.com2012-07-02T18:37:59Zurn:sha1:49589f0d0e35f643e697ab7ae8a51a530d38b0d8
versions of Bash. In addition, I can back out the change to the lit
built-in shell test runner to support this.
This should fix the majority of fallout on Darwin, but I suspect there
will be a few straggling issues.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@159544 91177308-0d34-0410-b5e6-96231b3b80d8
Enable the new LoopInfo algorithm by default.2012-06-26T04:11:38ZAndrew Trickatrick@apple.com2012-06-26T04:11:38Zurn:sha1:c9b1e25493b393013b28e5d457f2fb2845a4dd9f
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
Do not pass an invalid domtree to SimplifyInstruction from2012-05-20T01:32:09ZPeter Collingbournepeter@pcc.me.uk2012-05-20T01:32:09Zurn:sha1:fcaf5fa89cafe66d2659b711e7c190f3851f4ac5
LoopUnswitch. Fixes PR12887.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@157140 91177308-0d34-0410-b5e6-96231b3b80d8
Second attempt at PR12573:2012-04-30T10:44:54ZBill Wendlingisanbard@gmail.com2012-04-30T10:44:54Zurn:sha1:bfbab99b58aa530d5d6aa886ef66be42a047c756
Allow the "SplitCriticalEdge" function to split the edge to a landing pad. If
the pass is *sure* that it thinks it knows what it's doing, then it may go ahead
and specify that the landing pad can have its critical edge split. The loop
unswitch pass is one of these passes. It will split the critical edges of all
edges coming from a loop to a landing pad not within the loop. Doing so will
retain important loop analysis information, such as loop simplify.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@155817 91177308-0d34-0410-b5e6-96231b3b80d8
Fix 12513: Loop unrolling breaks with indirect branches.2012-04-10T05:14:42ZAndrew Trickatrick@apple.com2012-04-10T05:14:42Zurn:sha1:d9fc1ce8096f7138c60edc3a6655583bf209780e
Take this opportunity to generalize the indirectbr bailout logic for
loop transformations. CFG transformations will never get indirectbr
right, and there's no point trying.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@154386 91177308-0d34-0410-b5e6-96231b3b80d8
Fast fix for PR12343:2012-04-02T17:16:45ZStepan Dyatkovskiystpworld@narod.ru2012-04-02T17:16:45Zurn:sha1:aad9c3f17a73b3104f4a3673a2dc511a4878e20e
http://llvm.org/bugs/show_bug.cgi?id=12343
We have not trivial way for splitting edges that are goes from indirect branch. We can do it with some tricks, but it should be additionally discussed. And it is still dangerous due to difficulty of indirect branches controlling.
Fix forbids this case for unswitching.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@153879 91177308-0d34-0410-b5e6-96231b3b80d8
Replace all instances of dg.exp file with lit.local.cfg, since all tests are run with LIT now and now Dejagnu. dg.exp is no longer needed.2012-02-16T06:28:33ZEli Benderskyeli.bendersky@intel.com2012-02-16T06:28:33Zurn:sha1:0f0c411079cd21bb3a81a1b70bf8c67539a16c22
Patch reviewed by Daniel Dunbar. It will be followed by additional cleanup patches.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@150664 91177308-0d34-0410-b5e6-96231b3b80d8
Improved compile time:2012-01-11T08:40:51ZStepan Dyatkovskiystpworld@narod.ru2012-01-11T08:40:51Zurn:sha1:88c5c42c5c832f599b34a5f5f4d361b9c1eacf6c
1. Size heuristics changed. Now we calculate number of unswitching
branches only once per loop.
2. Some checks was moved from UnswitchIfProfitable to
processCurrentLoop, since it is not changed during processCurrentLoop
iteration. It allows decide to skip some loops at an early stage.
Extended statistics:
- Added total number of instructions analyzed.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@147935 91177308-0d34-0410-b5e6-96231b3b80d8
Reinstate r146578; it doesn't appear to be the cause of some recent execution-2011-12-22T21:06:36ZChad Rosiermcrosier@apple.com2011-12-22T21:06:36Zurn:sha1:f1eba253038ab480abb43ea33909e9095b1321a7
time regressions. In general, it is beneficial to compile-time.
Original commit message:
Fix for bug #11429: Wrong behaviour for switches. Small improvement for code
size heuristics.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@147175 91177308-0d34-0410-b5e6-96231b3b80d8