commit ba5409a6fd1f9e6a95b740e2eb28bdaf57ed3747
author Andreas Haas <ahaas@chromium.org> Tue Mar 20 14:19:33 2018
committer Commit Bot <commit-bot@chromium.org> Wed Mar 21 09:56:12 2018
tree df879c297245b9b3439f96e45f39c9eb337b7ce2
parent 3ba29d55905cbf5ccef9c4db9b9ccd0d64493f7f

[wasm] Make multi-return tests wasm-specific

The multi-return tests and fuzzer used a custom call descriptor which
was based on the default RegisterConfiguration. This meant that for the
tests, all available registers could be used to pass parameters and to
return values. This caused a problem, because in some cases we need a
scratch register in the frame deconstruction.

With this CL I change both the tests and the fuzzer to use the
WebAssembly call descriptor. Thereby we only use 2 registers for
returns, and one of the other registers can be used as scratch
register.

WebAssembly is the only use case at the moment which wants to return
values not only through registers but also over the stack. Therefore
I think it's acceptable to only test the WebAssembly usecase.

R=mstarzinger@chromium.org

Bug: chromium:813288
Change-Id: I31bed757af5f3e8589d2b3dfb6f0112ddecd1a20
Reviewed-on: https://chromium-review.googlesource.com/970656
Reviewed-by: Michael Starzinger <mstarzinger@chromium.org>
Commit-Queue: Andreas Haas <ahaas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#52099}