Revert of [wasm] Initial signal handler

Revert of [wasm] Initial signal handler (patchset #56 id:1090001 of https://codereview.chromium.org/2371833007/ )

Reason for revert:
Breaks tree, i.e. https://build.chromium.org/p/client.v8/builders/V8%20Linux64%20ASAN/builds/18928/steps/Check/logs/grow-memory

Original issue's description:
> [wasm] Initial signal handler
> 
> This is basically the minimum viable signal handler for Wasm bounds checks.
> It includes the TLS check and the fine grained instructions checks. These
> two checks provide most of the safety for the signal handler. Future CLs will
> add code range and data range checks for more robustness.
> 
> The trap handling code and data structures are all in src/trap-handler, with
> the code that actually runs in the signal handler confined to
> src/trap-handler/signal-handler.cc.
> 
> This changes adds a new V8 API that the embedder should call from a signal 
> handler that will give V8 the chance to handle the fault first. For hosts that
> do not want to implement their own signal handler, we include the option to
> install a simple one. This simple handler is also used for the tests.
> 
> When a Wasm module is instantiated, information about each function is passed
> to the trap handler, which is used to classify faults. These are removed during
> the instance finalizer.
> 
> Several future enhancements are planned before turning this on by default.
> Obviously, the additional checks will be added to MaybeHandleFault. We are
> also planning to add a two-level CodeObjectData table that is grouped by
> isolates to make cleanup easier and also reduce potential for contending on
> a single data structure.
> 
> BUG= https://bugs.chromium.org/p/v8/issues/detail?id=5277
> 
> Review-Url: https://codereview.chromium.org/2371833007
> Cr-Commit-Position: refs/heads/master@{#43523}
> Committed: https://chromium.googlesource.com/v8/v8/+/a5af7fe9ee388a636675f4a6872b1d34fa7d1a7a

TBR=ahaas@chromium.org,bradnelson@google.com,hpayer@chromium.org,jochen@chromium.org,mark@chromium.org,mseaborn@chromium.org,titzer@chromium.org,eholk@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG= https://bugs.chromium.org/p/v8/issues/detail?id=5277

Review-Url: https://codereview.chromium.org/2723133003
Cr-Commit-Position: refs/heads/master@{#43525}
Committed: https://chromium.googlesource.com/v8/v8/+/0b3e554e037d0a17e155294b7b2c02166e092e4c

[Benedikt Meurer, 2017-03-01 19:47:06]

The CQ bit was checked by bmeurer@chromium.org

[Benedikt Meurer, 2017-03-01 19:47:06]

Created Revert of [wasm] Initial signal handler

[commit-bot: I haz the power, 2017-03-01 19:47:17]

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-03-01 19:47:29]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1488397626271400, "parent_rev":
"19f24d6ef5ac652a444664d75fd1c52cd96cff2a", "commit_rev":
"0b3e554e037d0a17e155294b7b2c02166e092e4c"}

[commit-bot: I haz the power, 2017-03-01 19:47:34]

Description was changed from

==========
Revert of [wasm] Initial signal handler (patchset #56 id:1090001 of
https://codereview.chromium.org/2371833007/ )

Reason for revert:
Breaks tree, i.e.
https://build.chromium.org/p/client.v8/builders/V8%20Linux64%20ASAN/builds/18...

Original issue's description:
> [wasm] Initial signal handler
> 
> This is basically the minimum viable signal handler for Wasm bounds checks.
> It includes the TLS check and the fine grained instructions checks. These
> two checks provide most of the safety for the signal handler. Future CLs will
> add code range and data range checks for more robustness.
> 
> The trap handling code and data structures are all in src/trap-handler, with
> the code that actually runs in the signal handler confined to
> src/trap-handler/signal-handler.cc.
> 
> This changes adds a new V8 API that the embedder should call from a signal 
> handler that will give V8 the chance to handle the fault first. For hosts that
> do not want to implement their own signal handler, we include the option to
> install a simple one. This simple handler is also used for the tests.
> 
> When a Wasm module is instantiated, information about each function is passed
> to the trap handler, which is used to classify faults. These are removed
during
> the instance finalizer.
> 
> Several future enhancements are planned before turning this on by default.
> Obviously, the additional checks will be added to MaybeHandleFault. We are
> also planning to add a two-level CodeObjectData table that is grouped by
> isolates to make cleanup easier and also reduce potential for contending on
> a single data structure.
> 
> BUG= https://bugs.chromium.org/p/v8/issues/detail?id=5277
> 
> Review-Url: https://codereview.chromium.org/2371833007
> Cr-Commit-Position: refs/heads/master@{#43523}
> Committed:
https://chromium.googlesource.com/v8/v8/+/a5af7fe9ee388a636675f4a6872b1d34fa7...

TBR=ahaas@chromium.org,bradnelson@google.com,hpayer@chromium.org,jochen@chrom...
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG= https://bugs.chromium.org/p/v8/issues/detail?id=5277
==========

to

==========
Revert of [wasm] Initial signal handler (patchset #56 id:1090001 of
https://codereview.chromium.org/2371833007/ )

Reason for revert:
Breaks tree, i.e.
https://build.chromium.org/p/client.v8/builders/V8%20Linux64%20ASAN/builds/18...

Original issue's description:
> [wasm] Initial signal handler
> 
> This is basically the minimum viable signal handler for Wasm bounds checks.
> It includes the TLS check and the fine grained instructions checks. These
> two checks provide most of the safety for the signal handler. Future CLs will
> add code range and data range checks for more robustness.
> 
> The trap handling code and data structures are all in src/trap-handler, with
> the code that actually runs in the signal handler confined to
> src/trap-handler/signal-handler.cc.
> 
> This changes adds a new V8 API that the embedder should call from a signal 
> handler that will give V8 the chance to handle the fault first. For hosts that
> do not want to implement their own signal handler, we include the option to
> install a simple one. This simple handler is also used for the tests.
> 
> When a Wasm module is instantiated, information about each function is passed
> to the trap handler, which is used to classify faults. These are removed
during
> the instance finalizer.
> 
> Several future enhancements are planned before turning this on by default.
> Obviously, the additional checks will be added to MaybeHandleFault. We are
> also planning to add a two-level CodeObjectData table that is grouped by
> isolates to make cleanup easier and also reduce potential for contending on
> a single data structure.
> 
> BUG= https://bugs.chromium.org/p/v8/issues/detail?id=5277
> 
> Review-Url: https://codereview.chromium.org/2371833007
> Cr-Commit-Position: refs/heads/master@{#43523}
> Committed:
https://chromium.googlesource.com/v8/v8/+/a5af7fe9ee388a636675f4a6872b1d34fa7...

TBR=ahaas@chromium.org,bradnelson@google.com,hpayer@chromium.org,jochen@chrom...
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG= https://bugs.chromium.org/p/v8/issues/detail?id=5277

Review-Url: https://codereview.chromium.org/2723133003
Cr-Commit-Position: refs/heads/master@{#43525}
Committed:
https://chromium.googlesource.com/v8/v8/+/0b3e554e037d0a17e155294b7b2c02166e0...
==========

[commit-bot: I haz the power, 2017-03-01 19:47:35]

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