[webkit-changes] [WebKit/WebKit] e00720: Baseline JIT execution tracing code should get op_...

[EWS]

  Branch: refs/heads/main
  Home:   https://github.com/WebKit/WebKit
  Commit: e00720c9b6f9eade3780887ae617458c70d20689
      https://github.com/WebKit/WebKit/commit/e00720c9b6f9eade3780887ae617458c70d20689
  Author: Mark Lam <mark.lam at apple.com>
  Date:   2023-01-18 (Wed, 18 Jan 2023)

  Changed paths:
    A JSTests/wasm/stress/throw-from-wasm-catch-in-baseline-JIT-payload.bin
    A JSTests/wasm/stress/throw-from-wasm-catch-in-baseline-JIT.js
    M Source/JavaScriptCore/jit/JIT.cpp

  Log Message:
  -----------
  Baseline JIT execution tracing code should get op_catch callFrame from VM::callFrameForCatch.
https://bugs.webkit.org/show_bug.cgi?id=250755
<rdar://problem/98323960>

Reviewed by Yusuke Suzuki.

The initial callFrame on entry to the baseline JIT generated code for the op_catch opcode is
that of the exception thrower, not the exception catcher frame which corresponds to the baseline
JIT codeBlock being executed.  Hence, for op_catch, the execution trace dumper should get the
callFrame from VM::callFrameForCatch instead.

* JSTests/wasm/stress/throw-from-wasm-catch-in-baseline-JIT-payload.bin: Added.
* JSTests/wasm/stress/throw-from-wasm-catch-in-baseline-JIT.js: Added.
(foo):
* Source/JavaScriptCore/jit/JIT.cpp:
(JSC::JIT::privateCompileMainPass):

Canonical link: https://commits.webkit.org/259029@main