[turbofan] Unship try-catch.

[turbofan] Unship try-catch.

R=jkummerow@chromium.org

Committed: https://crrev.com/c268aea4fbb74b03a788fba020705594d669efb8
Cr-Commit-Position: refs/heads/master@{#34358}

[Jakob Kummerow, 2016-02-29 10:53:19]

lgtm

[Jakob Kummerow, 2016-02-29 10:59:45]

The CQ bit was checked by jkummerow@chromium.org

[commit-bot: I haz the power, 2016-02-29 10:59:49]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1748613002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1748613002/1

[commit-bot: I haz the power, 2016-02-29 11:10:14]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-02-29 11:10:50]

Description was changed from

==========
[turbofan] Unship try-catch.

R=jkummerow@chromium.org
==========

to

==========
[turbofan] Unship try-catch.

R=jkummerow@chromium.org

Committed: https://crrev.com/c268aea4fbb74b03a788fba020705594d669efb8
Cr-Commit-Position: refs/heads/master@{#34358}
==========

[commit-bot: I haz the power, 2016-02-29 11:10:50]

Patchset 1 (id:??) landed as
https://crrev.com/c268aea4fbb74b03a788fba020705594d669efb8
Cr-Commit-Position: refs/heads/master@{#34358}

[Jarin, 2016-03-08 08:02:02]

How about giving some reason for the revert? I am sure it would not be too much
work to mention an issue id, or link to chrome crash or some such. (Or at least
CC me?)

[Jakob Kummerow, 2016-03-08 09:02:01]

On 2016/03/08 08:02:02, Jarin wrote:
> How about giving some reason for the revert? I am sure it would not be too
much
> work to mention an issue id, or link to chrome crash or some such. (Or at
least
> CC me?)

Benedikt said there were known issues with try-catch; in fact he was surprised
to find out that we were shipping it. He said that the plan had been to turn it
on briefly for Canary coverage and then turn it off again while issues are being
fixed. (I forgot the specifics, sorry.)

[Benedikt Meurer, 2016-03-08 09:17:28]

The reason is that there are correctness issues with some lowerings, where we do
not properly handle the exception edges in every case. I fixed a few of them
some time ago, but there are probably more of them left, and we haven't had the
time to go through the lowerings before the release and add proper test cases
for everything.