[interpreter] Add ReThrow bytecode for try-finally support.

[interpreter] Add ReThrow bytecode for try-finally support.

This adds an explicit ReThrow bytecode to be used in the modelling of
try-finally statements. An exception that is being re-thrown should not
trigger message object creation or location computation and hence cannot
use the existing Throw bytecode.

R=rmcilroy@chromium.org
TEST=cctest/test-interpreter/InterpreterTryFinally
BUG=v8:4674
LOG=n

Committed: https://crrev.com/475d178f2e10c70f20dd2f4f397073f3a70298a0
Cr-Commit-Position: refs/heads/master@{#33472}

[rmcilroy, 2016-01-22 12:21:40]

You will need to add a call to builder()->ReThrow() in
BytecodeArrayBuilderTest::AllBytecodesGenerated too, otherwise it will fail.

Otherwise LGTM

[Michael Starzinger, 2016-01-22 16:18:28]

The CQ bit was checked by mstarzinger@chromium.org

[Michael Starzinger, 2016-01-22 16:18:28]

The patchset sent to the CQ was uploaded after l-g-t-m from
rmcilroy@chromium.org
Link to the patchset: https://codereview.chromium.org/1621673002/#ps40001
(title: "Rebased.")

[commit-bot: I haz the power, 2016-01-22 16:18:37]

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

[commit-bot: I haz the power, 2016-01-22 16:25:52]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2016-01-22 16:26:23]

Description was changed from

==========
[interpreter] Add ReThrow bytecode for try-finally support.

This adds an explicit ReThrow bytecode to be used in the modelling of
try-finally statements. An exception that is being re-thrown should not
trigger message object creation or location computation and hence cannot
use the existing Throw bytecode.

R=rmcilroy@chromium.org
TEST=cctest/test-interpreter/InterpreterTryFinally
BUG=v8:4674
LOG=n
==========

to

==========
[interpreter] Add ReThrow bytecode for try-finally support.

This adds an explicit ReThrow bytecode to be used in the modelling of
try-finally statements. An exception that is being re-thrown should not
trigger message object creation or location computation and hence cannot
use the existing Throw bytecode.

R=rmcilroy@chromium.org
TEST=cctest/test-interpreter/InterpreterTryFinally
BUG=v8:4674
LOG=n

Committed: https://crrev.com/475d178f2e10c70f20dd2f4f397073f3a70298a0
Cr-Commit-Position: refs/heads/master@{#33472}
==========

[commit-bot: I haz the power, 2016-01-22 16:26:23]

Patchset 3 (id:??) landed as
https://crrev.com/475d178f2e10c70f20dd2f4f397073f3a70298a0
Cr-Commit-Position: refs/heads/master@{#33472}