• fpizlo@apple.com's avatar
    Interpreter::unwind() has no need for the bytecodeOffset · f825bf66
    fpizlo@apple.com authored
    Reviewed by Oliver Hunt.
    It was only using the bytecodeOffset for some debugger stuff, but the debugger could
    just get the bytecodeOffset the same way the rest of the machinery does: by using the
    CallFrame's location.
    It turns out that a lot of really ugly code was in place just to supply this
    bytecodeOffset. This patch kills most of that code, and allows us to kill even more
    code in a future patch - though most likely that killage will involve further
    refactorings as well, see https://bugs.webkit.org/show_bug.cgi?id=121734.
    * dfg/DFGOperations.cpp:
    * interpreter/CallFrame.cpp:
    * interpreter/CallFrame.h:
    * interpreter/Interpreter.cpp:
    * interpreter/Interpreter.h:
    * jit/JITExceptions.cpp:
    * jit/JITExceptions.h:
    * jit/JITStubs.cpp:
    * llint/LLIntExceptions.cpp:
    * llint/LLIntExceptions.h:
    * llint/LLIntSlowPaths.cpp:
    * runtime/CommonSlowPaths.cpp:
    * runtime/CommonSlowPathsExceptions.cpp:
    * runtime/CommonSlowPathsExceptions.h:
    git-svn-id: http://svn.webkit.org/repository/webkit/trunk@156242 268f45cc-cd09-0410-ab3c-d52691b4dbfc