Revert of [wasm] Initial signal handler

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

Reason for revert:
ASAN breakage, such as https://build.chromium.org/p/client.v8/builders/V8%20Linux64%20ASAN/builds/19111/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-Original-Commit-Position: refs/heads/master@{#43523}
> Committed: https://chromium.googlesource.com/v8/v8/+/a5af7fe9ee388a636675f4a6872b1d34fa7d1a7a
> Review-Url: https://codereview.chromium.org/2371833007
> Cr-Commit-Position: refs/heads/master@{#43755}
> Committed: https://chromium.googlesource.com/v8/v8/+/338622d7cae787a63cece1f2e79a8b030023940b

TBR=ahaas@chromium.org,bradnelson@google.com,hpayer@chromium.org,jochen@chromium.org,mark@chromium.org,mseaborn@chromium.org,titzer@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/2744383002
Cr-Commit-Position: refs/heads/master@{#43757}
Committed: https://chromium.googlesource.com/v8/v8/+/aba151b92fbd45763160c046ae75e1505c1ca4cf

[Eric Holk, 2017-03-13 19:57:05]

The CQ bit was checked by eholk@chromium.org

[Eric Holk, 2017-03-13 19:57:05]

Created Revert of [wasm] Initial signal handler

[commit-bot: I haz the power, 2017-03-13 19:57:12]

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-13 19:57:13]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-03-13 19:57:14]

No L-G-T-M from a valid reviewer yet. 
CQ run can only be started by full committers or once the patch has
received an L-G-T-M from a full committer.
Even if an L-G-T-M may have been provided, it was from a non-committer,
_not_ a full super star committer.
Committers are members of the group "project-v8-committers".
Note that this has nothing to do with OWNERS files.

[bradn, 2017-03-13 20:02:38]

The CQ bit was checked by bradnelson@google.com

[commit-bot: I haz the power, 2017-03-13 20:02:43]

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-13 20:02:44]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-03-13 20:02:45]

No L-G-T-M from a valid reviewer yet. 
CQ run can only be started by full committers or once the patch has
received an L-G-T-M from a full committer.
Even if an L-G-T-M may have been provided, it was from a non-committer,
_not_ a full super star committer.
Committers are members of the group "project-v8-committers".
Note that this has nothing to do with OWNERS files.

[bradnelson, 2017-03-13 20:03:06]

bradnelson@chromium.org changed reviewers:
+ bradnelson@chromium.org

[bradnelson, 2017-03-13 20:03:06]

The CQ bit was checked by bradnelson@chromium.org

[bradnelson, 2017-03-13 20:03:06]

lgtm

[commit-bot: I haz the power, 2017-03-13 20:03:13]

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-13 20:03:27]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1489435386187600, "parent_rev":
"d3f236fa054413e9a81c95aef620605968282a82", "commit_rev":
"aba151b92fbd45763160c046ae75e1505c1ca4cf"}

[commit-bot: I haz the power, 2017-03-13 20:03:32]

Description was changed from

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

Reason for revert:
ASAN breakage, such as
https://build.chromium.org/p/client.v8/builders/V8%20Linux64%20ASAN/builds/19...

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-Original-Commit-Position: refs/heads/master@{#43523}
> Committed:
https://chromium.googlesource.com/v8/v8/+/a5af7fe9ee388a636675f4a6872b1d34fa7...
> Review-Url: https://codereview.chromium.org/2371833007
> Cr-Commit-Position: refs/heads/master@{#43755}
> Committed:
https://chromium.googlesource.com/v8/v8/+/338622d7cae787a63cece1f2e79a8b03002...

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 #60 id:1170001 of
https://codereview.chromium.org/2371833007/ )

Reason for revert:
ASAN breakage, such as
https://build.chromium.org/p/client.v8/builders/V8%20Linux64%20ASAN/builds/19...

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-Original-Commit-Position: refs/heads/master@{#43523}
> Committed:
https://chromium.googlesource.com/v8/v8/+/a5af7fe9ee388a636675f4a6872b1d34fa7...
> Review-Url: https://codereview.chromium.org/2371833007
> Cr-Commit-Position: refs/heads/master@{#43755}
> Committed:
https://chromium.googlesource.com/v8/v8/+/338622d7cae787a63cece1f2e79a8b03002...

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/2744383002
Cr-Commit-Position: refs/heads/master@{#43757}
Committed:
https://chromium.googlesource.com/v8/v8/+/aba151b92fbd45763160c046ae75e1505c1...
==========

[commit-bot: I haz the power, 2017-03-13 20:03:34]

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