titzer 45d75bca5c [turbofan] Handle dead diamonds in scheduling and add a test. ... The background here is that graphs generated from WASM are not trimmed. That means there can be some floating control diamonds that are not reachable from end. An assertion in the scheduler for phis from floating diamonds checks that the use edge in this situation is the control edge, but in general, any edge could cause this. Scheduling still works without this assertion. The longer term fix is to either trim the graphs (more compile time overhead for WASM) or improve the scheduler's handling of dead code in the graph. Currently it does not schedule dead code but the potential use positions of dead code are used in the computation of the common dominator of uses. We could recognize dead nodes in PrepareUses() and check in GetBlockForUse() as per TODO. R=bradnelson@chromium.org, mstarzinger@chromium.org BUG= Review URL: https://codereview.chromium.org/1846933002 Cr-Commit-Position: refs/heads/master@{#35245}		2016-04-04 17:45:59 +00:00
..
OWNERS	Adding OWNERS files to test directories for wasm.	2015-12-14 14:22:15 +00:00
test-run-wasm-64.cc	Fixed rotate left on windows.	2016-04-01 09:52:13 +00:00
test-run-wasm-js.cc	[wasm] Fix arm64 frame alignment.	2016-03-29 11:42:48 +00:00
test-run-wasm-module.cc	Expose a lower bound of malloc'd memory via heap statistics	2016-04-01 10:01:56 +00:00
test-run-wasm.cc	[turbofan] Handle dead diamonds in scheduling and add a test.	2016-04-04 17:45:59 +00:00
test-signatures.h	[wasm] Add utilities to print out WASM ast directly from the bytes.	2016-01-21 16:11:19 +00:00
wasm-run-utils.h	Expose a lower bound of malloc'd memory via heap statistics	2016-04-01 10:01:56 +00:00