[wasm] Decoder had 2 representations for "end".

[wasm] Decoder had 2 representations for "end".

Removing "limit_", using just "end_".

BUG=

Review-Url: https://codereview.chromium.org/2613193002
Cr-Commit-Position: refs/heads/master@{#42105}
Committed: https://chromium.googlesource.com/v8/v8/+/a6402fd91667fbb955e5f990c70e09c32770ecea

[Mircea Trofin, 2017-01-06 04:19:47]

The CQ bit was checked by mtrofin@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-01-06 04:19:55]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[Mircea Trofin, 2017-01-06 04:23:25]

Description was changed from

==========
[wasm] Decoder had 2 representations for "end".

Removing "limit_", using just "end_".

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

to

==========
[wasm] Decoder had 2 representations for "end".

Removing "limit_", using just "end_".

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

[Mircea Trofin, 2017-01-06 04:23:25]

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

[commit-bot: I haz the power, 2017-01-06 04:45:30]

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

[commit-bot: I haz the power, 2017-01-06 04:45:31]

Dry run: This issue passed the CQ dry run.

[bradnelson, 2017-01-06 08:00:24]

The CQ bit was checked by bradnelson@chromium.org

[bradnelson, 2017-01-06 08:00:25]

lgtm

[commit-bot: I haz the power, 2017-01-06 08:00:34]

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-01-06 08:02:11]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1483689624652280, "parent_rev":
"c8d8bf215044aaafde1a2213f48b5629fb57c5bf", "commit_rev":
"a6402fd91667fbb955e5f990c70e09c32770ecea"}

[commit-bot: I haz the power, 2017-01-06 08:02:16]

Description was changed from

==========
[wasm] Decoder had 2 representations for "end".

Removing "limit_", using just "end_".

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

to

==========
[wasm] Decoder had 2 representations for "end".

Removing "limit_", using just "end_".

BUG=

Review-Url: https://codereview.chromium.org/2613193002
Cr-Commit-Position: refs/heads/master@{#42105}
Committed:
https://chromium.googlesource.com/v8/v8/+/a6402fd91667fbb955e5f990c70e09c3277...
==========

[commit-bot: I haz the power, 2017-01-06 08:02:17]

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

[titzer, 2017-01-09 18:34:46]

On 2017/01/06 08:02:17, commit-bot: I haz the power wrote:
> Committed patchset #1 (id:1) as
>
https://chromium.googlesource.com/v8/v8/+/a6402fd91667fbb955e5f990c70e09c3277...

There was a good reason for {limit} being separate from {end}. {limit} is
checked in decoding loops and is reset when an error occurs, terminating
decoding loops, whereas {end} always points to the end of the bytes, and should
never change.

[Mircea Trofin, 2017-01-09 19:00:17]

On 2017/01/09 18:34:46, titzer wrote:
> On 2017/01/06 08:02:17, commit-bot: I haz the power wrote:
> > Committed patchset #1 (id:1) as
> >
>
https://chromium.googlesource.com/v8/v8/+/a6402fd91667fbb955e5f990c70e09c3277...
> 
> There was a good reason for {limit} being separate from {end}. {limit} is
> checked in decoding loops and is reset when an error occurs, terminating
> decoding loops, whereas {end} always points to the end of the bytes, and
should
> never change.

What scenario would we want to support with that separation, and what should the
test be?