PPC/s390: [wasm] Do not use setjmp/longjmp in cctests.

PPC/s390: [wasm] Do not use setjmp/longjmp in cctests.

Port 79570f87a1b467846a51c60186e4707f68a4d3d0

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}
Committed: https://chromium.googlesource.com/v8/v8/+/13042c9a19b58909905da23129ea5445f8e050db

[JaideepBajwa, 2017-02-10 13:52:28]

ptal

[john.yan, 2017-02-10 15:07:21]

lgtm

[JaideepBajwa, 2017-02-10 15:09:51]

The CQ bit was checked by bjaideep@ca.ibm.com

[commit-bot: I haz the power, 2017-02-10 15:09:56]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-02-10 15:36:45]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1486739391984430, "parent_rev":
"218e3ed09f3fdb0591a92014906b2a4ad671c08e", "commit_rev":
"13042c9a19b58909905da23129ea5445f8e050db"}

[commit-bot: I haz the power, 2017-02-10 15:36:49]

Description was changed from

==========
PPC/s390: [wasm] Do not use setjmp/longjmp in cctests.

Port 79570f87a1b467846a51c60186e4707f68a4d3d0

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
==========

to

==========
PPC/s390: [wasm] Do not use setjmp/longjmp in cctests.

Port 79570f87a1b467846a51c60186e4707f68a4d3d0

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}
Committed:
https://chromium.googlesource.com/v8/v8/+/13042c9a19b58909905da23129ea5445f8e...
==========

[commit-bot: I haz the power, 2017-02-10 15:36:50]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/v8/v8/+/13042c9a19b58909905da23129ea5445f8e...