• ahaas's avatar
    [wasm] Do not use setjmp/longjmp in cctests. · 79570f87
    ahaas authored
    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=titzer@chromium.org, clemensh@chromium.org, v8-arm-ports@googlegroups.com
    CC=jarin@chromium.org
    
    Review-Url: https://codereview.chromium.org/2685583003
    Cr-Commit-Position: refs/heads/master@{#43095}
    79570f87
Name
Last commit
Last update
..
OWNERS Loading commit data...
code-generator-mips.cc Loading commit data...
instruction-codes-mips.h Loading commit data...
instruction-scheduler-mips.cc Loading commit data...
instruction-selector-mips.cc Loading commit data...