Ignore:
Timestamp:
Dec 16, 2015, 11:10:55 AM (9 years ago)
Author:
[email protected]
Message:

Work around a bug in LLVM by flipping the unification order
https://bugs.webkit.org/show_bug.cgi?id=152341
rdar://problem/23920749

Reviewed by Mark Lam.

  • dfg/DFGUnificationPhase.cpp:

(JSC::DFG::UnificationPhase::run):

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/Source/JavaScriptCore/dfg/DFGUnificationPhase.cpp

    r193782 r194164  
    6060                    if (!phi->children.child(childIdx))
    6161                        break;
    62                    
    63                     phi->children.child(childIdx)->variableAccessData()->unify(phi->variableAccessData());
     62
     63                    // We'd like to reverse the order of unification because it helps to reveal
     64                    // more bugs on our end, though it's otherwise not observable. But we do it
     65                    // this way because it works around a bug in open source LLVM's live-outs
     66                    // computation.
     67                    phi->variableAccessData()->unify(phi->children.child(childIdx)->variableAccessData());
    6468                }
    6569            }
Note: See TracChangeset for help on using the changeset viewer.