diff options
| author | Daniel Jasper <djasper@google.com> | 2015-03-03 10:23:11 +0000 |
|---|---|---|
| committer | Daniel Jasper <djasper@google.com> | 2015-03-03 10:23:11 +0000 |
| commit | 8f239f83b033b50294f21bbca7e79ae4b1ccb1ca (patch) | |
| tree | b2208f05f71103a2c71f40d96e8be8b8560acd9b /llvm/lib/Analysis/ModuleDebugInfoPrinter.cpp | |
| parent | 34d761d893e0126c415d7b17f7474a3bef2beaa2 (diff) | |
| download | llvm-8f239f83b033b50294f21bbca7e79ae4b1ccb1ca.zip llvm-8f239f83b033b50294f21bbca7e79ae4b1ccb1ca.tar.gz llvm-8f239f83b033b50294f21bbca7e79ae4b1ccb1ca.tar.bz2 | |
During PHI elimination, split critical edges that move copies out of loops.
This prevents the behavior observed in llvm.org/PR22369. I am not sure
whether I am reading the code correctly, but the early exit based on
isLiveOutPastPHIs() seems to make the wrong assumption that
RegisterCoalescer won't be able to coalesce those copies later.
This change hides the new behavior behind -no-phi-elim-live-out-early-exit
as it currently breaks four tests:
* Assertion in:
CodeGen/Hexagon/hwloop-cleanup.ll
* Worse code in:
CodeGen/X86/coalescer-commute4.ll
CodeGen/X86/phys_subreg_coalesce-2.ll
CodeGen/X86/zlib-longest-match.ll
The root cause here seems to be that the heuristic that determines
the visitation order in RegisterCoalescer gets less lucky.
llvm-svn: 231064
Diffstat (limited to 'llvm/lib/Analysis/ModuleDebugInfoPrinter.cpp')
0 files changed, 0 insertions, 0 deletions