Convince gcc that local variables in i::ValueDeserializer::ReadJSArrayBufferView are initialized.

Convince gcc that local variables in i::ValueDeserializer::ReadJSArrayBufferView are initialized.

It emits spurious -Wmaybe-uninitialized warnings. Initializing these variables
shouldn't do any harm (with an optimizing compiler), so this seems the quickest
way to mollify gcc.

BUG=chromium:148757
Committed: https://crrev.com/88d603bb550827b179a7f6cf67e9c16a6b2d5f60
Cr-Commit-Position: refs/heads/master@{#39000}

[jbroman, 2016-08-29 21:10:17]

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

[commit-bot: I haz the power, 2016-08-29 21:10:28]

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

[jbroman, 2016-08-29 21:12:27]

jbroman@chromium.org changed reviewers:
+ jkummerow@chromium.org, machenbach@chromium.org

[jbroman, 2016-08-29 21:12:28]

I can't reproduce the original error locally, even with is_clang=false, but it
seems clear that gcc simply isn't noticing that v8::Maybe<T>::To always
initializes if it returns true.

[jbroman, 2016-08-29 21:12:46]

(In response to https://codereview.chromium.org/2287653002/#msg21)

[commit-bot: I haz the power, 2016-08-29 21:33:28]

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

[commit-bot: I haz the power, 2016-08-29 21:33:29]

Dry run: This issue passed the CQ dry run.

[Jakob Kummerow, 2016-08-30 08:29:58]

The CQ bit was checked by jkummerow@chromium.org

[Jakob Kummerow, 2016-08-30 08:29:59]

lgtm

[commit-bot: I haz the power, 2016-08-30 08:30:10]

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, 2016-08-30 09:41:29]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-08-30 09:41:52]

Description was changed from

==========
Convince gcc that local variables in i::ValueDeserializer::ReadJSArrayBufferView
are initialized.

It emits spurious -Wmaybe-uninitialized warnings. Initializing these variables
shouldn't do any harm (with an optimizing compiler), so this seems the quickest
way to mollify gcc.

BUG=chromium:148757
==========

to

==========
Convince gcc that local variables in i::ValueDeserializer::ReadJSArrayBufferView
are initialized.

It emits spurious -Wmaybe-uninitialized warnings. Initializing these variables
shouldn't do any harm (with an optimizing compiler), so this seems the quickest
way to mollify gcc.

BUG=chromium:148757

Committed: https://crrev.com/88d603bb550827b179a7f6cf67e9c16a6b2d5f60
Cr-Commit-Position: refs/heads/master@{#39000}
==========

[commit-bot: I haz the power, 2016-08-30 09:41:53]

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