Clemens Hammacher 0738f0f668 [wasm] Move "thread in wasm" flag handling out of compiled code ... Instead of modifying this flag in compiled wasm code, we can just change it in the caller / called code. This saves code space and compilation time and fixes the referenced bug. R=titzer@chromium.org, eholk@chromium.org Bug: chromium:773631, v8:5277 Change-Id: I095158ac01eecd21a92649a3990e8d7c593db912 Reviewed-on: https://chromium-review.googlesource.com/712597 Reviewed-by: Ben Titzer <titzer@chromium.org> Reviewed-by: Eric Holk <eholk@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#48602}		2017-10-16 15:17:29 +00:00
..
DEPS	[wasm] Initial signal handler	2017-03-13 22:12:23 +00:00
handler-inside.cc	[wasm] Move "thread in wasm" flag handling out of compiled code	2017-10-16 15:17:29 +00:00
handler-outside.cc	Reland "Reland "[wasm] trap handlers: fall back on old signal handler""	2017-10-11 20:49:45 +00:00
handler-shared.cc	Reland "Reland "[wasm] trap handlers: fall back on old signal handler""	2017-10-11 20:49:45 +00:00
OWNERS	Add eholk to Wasm-related OWNERS files	2017-08-10 18:58:00 +00:00
trap-handler-internal.h	Reland "Reland "[wasm] trap handlers: fall back on old signal handler""	2017-10-11 20:49:45 +00:00
trap-handler.h	Reland "Reland "[wasm] trap handlers: fall back on old signal handler""	2017-10-11 20:49:45 +00:00