Ignore:
Timestamp:
Jun 21, 2012, 6:33:30 PM (13 years ago)
Author:
[email protected]
Message:

op_resolve_global should not prevent DFG inlining
https://bugs.webkit.org/show_bug.cgi?id=89726

Reviewed by Gavin Barraclough.

  • bytecode/CodeBlock.cpp:

(JSC::CodeBlock::CodeBlock):
(JSC::CodeBlock::shrinkToFit):

  • bytecode/GlobalResolveInfo.h:

(JSC::GlobalResolveInfo::GlobalResolveInfo):
(GlobalResolveInfo):

  • dfg/DFGByteCodeParser.cpp:

(JSC::DFG::ByteCodeParser::InlineStackEntry::InlineStackEntry):

  • dfg/DFGCapabilities.h:

(JSC::DFG::canInlineOpcode):

  • dfg/DFGOperations.cpp:
  • dfg/DFGOperations.h:
  • dfg/DFGSpeculativeJIT.h:

(JSC::DFG::SpeculativeJIT::callOperation):

  • dfg/DFGSpeculativeJIT32_64.cpp:

(JSC::DFG::SpeculativeJIT::compile):

  • dfg/DFGSpeculativeJIT64.cpp:

(JSC::DFG::SpeculativeJIT::compile):

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/Source/JavaScriptCore/bytecode/GlobalResolveInfo.h

    r120897 r120989  
    3232
    3333struct GlobalResolveInfo {
     34    GlobalResolveInfo() { }
     35   
    3436    GlobalResolveInfo(unsigned bytecodeOffset)
    3537        : offset(0)
     
    4042    WriteBarrier<Structure> structure;
    4143    unsigned offset;
    42     unsigned bytecodeOffset;
     44    unsigned bytecodeOffset; // Only valid in old JIT code. This means nothing in the DFG.
    4345};
    4446
Note: See TracChangeset for help on using the changeset viewer.