c77bb611e3
After the FallThruTo in kExprEnd, the current block {c} is never
unreachable. Hence, the check for {c->unreachable} afterwards can be
removed.
In the loop case, the {TypeCheckFallThru} already adds entries for
non-existing values to the stack, so no need to {PushEndValues}.
Also, add more tests for the loop case.
R=titzer@chromium.org
Change-Id: I8737affaeed2ea663bd6ddafa36532ca9a7379bb
Reviewed-on: https://chromium-review.googlesource.com/645859
Reviewed-by: Ben Titzer <titzer@chromium.org>
Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#47765}
|
||
|---|---|---|
| .. | ||
| OWNERS | ||
| test-c-wasm-entry.cc | ||
| test-run-wasm-64.cc | ||
| test-run-wasm-asmjs.cc | ||
| test-run-wasm-atomics.cc | ||
| test-run-wasm-interpreter.cc | ||
| test-run-wasm-js.cc | ||
| test-run-wasm-module.cc | ||
| test-run-wasm-relocation.cc | ||
| test-run-wasm-simd.cc | ||
| test-run-wasm.cc | ||
| test-wasm-breakpoints.cc | ||
| test-wasm-interpreter-entry.cc | ||
| test-wasm-stack.cc | ||
| test-wasm-trap-position.cc | ||
| wasm-run-utils.h | ||