Fix another gcc 4.9.2 sign-compare error.

Fix another gcc 4.9.2 sign-compare error.

BUG=

Committed: https://crrev.com/88a3cc79df57dc4604c2e15605e1240473f261e7
Cr-Commit-Position: refs/heads/master@{#31063}

[paul.l..., 2015-10-01 20:45:47]

The CQ bit was checked by paul.lind@imgtec.com to run a CQ dry run

[commit-bot: I haz the power, 2015-10-01 20:45:58]

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

[paul.l..., 2015-10-01 20:50:34]

paul.lind@imgtec.com changed reviewers:
+ jkummerow@chromium.org, oth@chromium.org, rmcilroy@chromium.org

[paul.l..., 2015-10-01 20:50:34]

PTAL. I looked at changing the return type of Bytecodes::NumberOfOperands() to
unsigned, but that will cause even more of these sign-difference DCHECK issues
(in other places).

[commit-bot: I haz the power, 2015-10-01 20:51:47]

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

[commit-bot: I haz the power, 2015-10-01 20:51:48]

Dry run: Try jobs failed on following builders:
  v8_win_nosnap_shared_compile_rel on tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_win_nosnap_shared_compil...)

[paul.l..., 2015-10-01 22:11:13]

paul.lind@imgtec.com changed reviewers:
+ machenbach@google.com

[paul.l..., 2015-10-01 22:11:13]

Michael, could you please look at the 2 failed try jobs? They appear to be
infrastructure issues in applying the patch.

[Michael Achenbach, 2015-10-02 06:41:08]

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

[commit-bot: I haz the power, 2015-10-02 06:41:14]

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

[Michael Achenbach, 2015-10-02 06:41:48]

On 2015/10/01 22:11:13, paul.l... wrote:
> Michael, could you please look at the 2 failed try jobs? They appear to be
> infrastructure issues in applying the patch.

Looks like those were both due to network failures. In that case lets just try
again...

[commit-bot: I haz the power, 2015-10-02 06:46:46]

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

[commit-bot: I haz the power, 2015-10-02 06:46:47]

Dry run: This issue passed the CQ dry run.

[rmcilroy, 2015-10-02 06:57:39]

Lgtm.

Apologies, looks like I lost your previous fix in rebasing. Thanks!

[rmcilroy, 2015-10-02 06:57:46]

The CQ bit was checked by rmcilroy@chromium.org

[commit-bot: I haz the power, 2015-10-02 06:57:59]

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

[commit-bot: I haz the power, 2015-10-02 06:59:50]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-10-02 07:00:08]

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