Ignore:
Timestamp:
May 20, 2015, 11:40:42 AM (10 years ago)
Author:
[email protected]
Message:

Add some assertions about the CFG in the loop pre-header creation phase
https://bugs.webkit.org/show_bug.cgi?id=145205

Reviewed by Geoffrey Garen.

  • dfg/DFGByteCodeParser.cpp:

(JSC::DFG::ByteCodeParser::currentNodeOrigin): Add a FIXME.

  • dfg/DFGLICMPhase.cpp:

(JSC::DFG::LICMPhase::run): Add a FIXME.

  • dfg/DFGLoopPreHeaderCreationPhase.cpp:

(JSC::DFG::LoopPreHeaderCreationPhase::run): Add the assertions.

File:
1 edited

Legend:

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

    r184405 r184646  
    131131            DFG_ASSERT(m_graph, preHeader->terminal(), preHeader->terminal()->op() == Jump);
    132132           
     133            // We should validate the pre-header. If we placed forExit origins on nodes only if
     134            // at the top of that node it is legal to exit, then we would simply check if Jump
     135            // had a forExit. We should disable hoisting to pre-headers that don't validate.
     136            // Or, we could only allow hoisting of things that definitely don't exit.
     137            // FIXME: https://bugs.webkit.org/show_bug.cgi?id=145204
     138           
    133139            data.preHeader = preHeader;
    134140        }
Note: See TracChangeset for help on using the changeset viewer.