[interpreter] Always 'continue' loops by jumping forward to end of body.

[interpreter] Always 'continue' loops by jumping forward to end of body.

We sometimes used to continue by jumping _back_ to the condition check at the
top of the loop. After my recent generator-related changes, that check is no
longer at the loop header, so a continue could create an additional loop. In
order to avoid this, we now always set the continue target to be the first
instruction following the loop body.

BUG=

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

[neis, 2016-05-04 13:26:25]

Description was changed from

==========
[interpreter] Always 'continue' loops by jumping forward to end of body.

We sometimes used to continue by jumping _back_ to the condition check at the
top of the loop. After my recent generator-related changes, that check is no
longer at the loop header, so a continue could create an additional loop. In
order to avoid this, we now always set the continue target to be the first
instruction following the loop body.

BUG=
==========

to

==========
[interpreter] Always 'continue' loops by jumping forward to end of body.

We sometimes used to continue by jumping _back_ to the condition check at the
top of the loop. After my recent generator-related changes, that check is no
longer at the loop header, so a continue could create an additional loop. In
order to avoid this, we now always set the continue target to be the first
instruction following the loop body.

BUG=
==========

[neis, 2016-05-04 13:26:25]

neis@chromium.org changed reviewers:
+ oth@chromium.org, rmcilroy@chromium.org

[neis, 2016-05-04 13:30:38]

PTAL.

Note that in the case that we eventually want to support 'continue' inside
do-expressions, we probably cannot avoid ending up in the situation where
continues create additional loops which then also require additional generator
state dispatches.

[rmcilroy, 2016-05-04 15:11:11]

Nice, LGTM assuming it works for Orion. Thanks.

[oth, 2016-05-04 15:21:33]

Super, lgtm, thanks!

[neis, 2016-05-04 15:25:38]

The CQ bit was checked by neis@chromium.org

[commit-bot: I haz the power, 2016-05-04 15:25:47]

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

[commit-bot: I haz the power, 2016-05-04 15:56:20]

Description was changed from

==========
[interpreter] Always 'continue' loops by jumping forward to end of body.

We sometimes used to continue by jumping _back_ to the condition check at the
top of the loop. After my recent generator-related changes, that check is no
longer at the loop header, so a continue could create an additional loop. In
order to avoid this, we now always set the continue target to be the first
instruction following the loop body.

BUG=
==========

to

==========
[interpreter] Always 'continue' loops by jumping forward to end of body.

We sometimes used to continue by jumping _back_ to the condition check at the
top of the loop. After my recent generator-related changes, that check is no
longer at the loop header, so a continue could create an additional loop. In
order to avoid this, we now always set the continue target to be the first
instruction following the loop body.

BUG=
==========

[commit-bot: I haz the power, 2016-05-04 15:56:21]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-05-04 15:57:49]

Description was changed from

==========
[interpreter] Always 'continue' loops by jumping forward to end of body.

We sometimes used to continue by jumping _back_ to the condition check at the
top of the loop. After my recent generator-related changes, that check is no
longer at the loop header, so a continue could create an additional loop. In
order to avoid this, we now always set the continue target to be the first
instruction following the loop body.

BUG=
==========

to

==========
[interpreter] Always 'continue' loops by jumping forward to end of body.

We sometimes used to continue by jumping _back_ to the condition check at the
top of the loop. After my recent generator-related changes, that check is no
longer at the loop header, so a continue could create an additional loop. In
order to avoid this, we now always set the continue target to be the first
instruction following the loop body.

BUG=

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

[commit-bot: I haz the power, 2016-05-04 15:57:50]

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