Ignore:
Timestamp:
Jan 27, 2015, 9:48:59 PM (11 years ago)
Author:
[email protected]
Message:

ExitSiteData saying m_takesSlowPath shouldn't mean early returning takesSlowPath() since for the non-LLInt case we later set m_couldTakeSlowPath, which is more precise
https://bugs.webkit.org/show_bug.cgi?id=140980

Reviewed by Oliver Hunt.

  • bytecode/CallLinkStatus.cpp:

(JSC::CallLinkStatus::computeFor):

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/Source/JavaScriptCore/bytecode/CallLinkStatus.cpp

    r173069 r179241  
    8787#if ENABLE(DFG_JIT)
    8888    ExitSiteData exitSiteData = computeExitSiteData(locker, profiledBlock, bytecodeIndex);
    89     if (exitSiteData.m_takesSlowPath)
    90         return takesSlowPath();
    9189   
    9290    CallLinkInfo* callLinkInfo = map.get(CodeOrigin(bytecodeIndex));
    93     if (!callLinkInfo)
     91    if (!callLinkInfo) {
     92        if (exitSiteData.m_takesSlowPath)
     93            return takesSlowPath();
    9494        return computeFromLLInt(locker, profiledBlock, bytecodeIndex);
     95    }
    9596   
    9697    return computeFor(locker, profiledBlock, *callLinkInfo, exitSiteData);
Note: See TracChangeset for help on using the changeset viewer.