-
bjaideep authored
Port 79570f87 Original Commit Message: The use of setjmp/longjmp makes the cctests in test-run-wasm and test-run-wasm-64 flaky on Windows, and I think that it is better not to use it. With this CL I replace it as follows: Similar to the setjmp/longjmp implementation we still call a C function when a trap happens. However, instead of calling longjmp in this C function we just set a flag which indicates that a trap happened and then return. After we return from the C function we leave the frame of the current wasm function and return with a RET instruction. At the end of a test the wasm test runner checks the flag to see if a trap happened. Please take a special look at the LeaveFrame function on arm64. R=ahaas@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com BUG= LOG=N Review-Url: https://codereview.chromium.org/2685303003 Cr-Commit-Position: refs/heads/master@{#43110}
13042c9a
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
OWNERS | ||
code-generator-s390.cc | ||
instruction-codes-s390.h | ||
instruction-scheduler-s390.cc | ||
instruction-selector-s390.cc |