Get v8 builds to use up-to-date VS toolchains

Get v8 builds to use up-to-date VS toolchains

The VS 2013 toolchain used by v8 is ~two months out of date. The
Chromium toolchain was updated in October to include the Windows 10
SDK. Using a different toolchain in v8 leads to the possibility of
odd incompatibilities, and means that switching between Chromium and
v8 requires a time-consuming reinstallation of the toolchain. The
VS 2013 toolchain was updated by crrev.com/1502563003.

The VS 2015 toolchain used by v8 is also out of date. It is the wrong
compiler version (RTM instead of Update 1), the wrong SDK version, and
it is missing files such as the UCRT installers.

LOG=N
BUG=440500, 491424
Committed: https://crrev.com/aa354d3f6ff1a8b5db9958cf54d3464fea023397
Cr-Commit-Position: refs/heads/master@{#33560}

[brucedawson, 2016-01-26 22:13:37]

Description was changed from

==========
Get v8 builds to use up-to-date VS toolchains

The VS 2013 toolchain used by v8 is ~two months out of date. The
Chromium toolchain was updated in October to include the Windows 10
SDK. Using a different toolchain in v8 leads to the possibility of
odd incompatibilities, and means that switching between Chromium and
v8 requires a time-consuming reinstallation of the toolchain. The
VS 2013 toolchain was updated by crrev.com/1502563003.

The VS 2015 toolchain used by v8 is also out of date. It is the wrong
compiler version (RTM instead of Update 1), the wrong SDK version, and
it is missing files such as the UCRT installers.

R=machenbach@chromium.org
LOG=N
BUG=440500,491424
==========

to

==========
Get v8 builds to use up-to-date VS toolchains

The VS 2013 toolchain used by v8 is ~two months out of date. The
Chromium toolchain was updated in October to include the Windows 10
SDK. Using a different toolchain in v8 leads to the possibility of
odd incompatibilities, and means that switching between Chromium and
v8 requires a time-consuming reinstallation of the toolchain. The
VS 2013 toolchain was updated by crrev.com/1502563003.

The VS 2015 toolchain used by v8 is also out of date. It is the wrong
compiler version (RTM instead of Update 1), the wrong SDK version, and
it is missing files such as the UCRT installers.

LOG=N
BUG=440500,491424
==========

[Michael Achenbach, 2016-01-27 08:16:20]

lgtm

I'd be nice if this file lived in the buildtools repo (for both chromium and v8
and everybody). Then it'd be updated automatically by our deps roller.

[brucedawson, 2016-01-27 17:53:55]

On 2016/01/27 08:16:20, Michael Achenbach wrote:
> lgtm
> 
> I'd be nice if this file lived in the buildtools repo (for both chromium and
v8
> and everybody). Then it'd be updated automatically by our deps roller.

Agreed. Manually synchronizing clearly doesn't work.

There are quite a few other differences that have popped up recently but this is
the only one that was causing problems.

[brucedawson, 2016-01-27 17:54:01]

The CQ bit was checked by brucedawson@chromium.org

[commit-bot: I haz the power, 2016-01-27 17:54:04]

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

[commit-bot: I haz the power, 2016-01-27 18:17:11]

Description was changed from

==========
Get v8 builds to use up-to-date VS toolchains

The VS 2013 toolchain used by v8 is ~two months out of date. The
Chromium toolchain was updated in October to include the Windows 10
SDK. Using a different toolchain in v8 leads to the possibility of
odd incompatibilities, and means that switching between Chromium and
v8 requires a time-consuming reinstallation of the toolchain. The
VS 2013 toolchain was updated by crrev.com/1502563003.

The VS 2015 toolchain used by v8 is also out of date. It is the wrong
compiler version (RTM instead of Update 1), the wrong SDK version, and
it is missing files such as the UCRT installers.

LOG=N
BUG=440500,491424
==========

to

==========
Get v8 builds to use up-to-date VS toolchains

The VS 2013 toolchain used by v8 is ~two months out of date. The
Chromium toolchain was updated in October to include the Windows 10
SDK. Using a different toolchain in v8 leads to the possibility of
odd incompatibilities, and means that switching between Chromium and
v8 requires a time-consuming reinstallation of the toolchain. The
VS 2013 toolchain was updated by crrev.com/1502563003.

The VS 2015 toolchain used by v8 is also out of date. It is the wrong
compiler version (RTM instead of Update 1), the wrong SDK version, and
it is missing files such as the UCRT installers.

LOG=N
BUG=440500,491424
==========

[commit-bot: I haz the power, 2016-01-27 18:17:11]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-01-27 18:18:13]

Description was changed from

==========
Get v8 builds to use up-to-date VS toolchains

The VS 2013 toolchain used by v8 is ~two months out of date. The
Chromium toolchain was updated in October to include the Windows 10
SDK. Using a different toolchain in v8 leads to the possibility of
odd incompatibilities, and means that switching between Chromium and
v8 requires a time-consuming reinstallation of the toolchain. The
VS 2013 toolchain was updated by crrev.com/1502563003.

The VS 2015 toolchain used by v8 is also out of date. It is the wrong
compiler version (RTM instead of Update 1), the wrong SDK version, and
it is missing files such as the UCRT installers.

LOG=N
BUG=440500,491424
==========

to

==========
Get v8 builds to use up-to-date VS toolchains

The VS 2013 toolchain used by v8 is ~two months out of date. The
Chromium toolchain was updated in October to include the Windows 10
SDK. Using a different toolchain in v8 leads to the possibility of
odd incompatibilities, and means that switching between Chromium and
v8 requires a time-consuming reinstallation of the toolchain. The
VS 2013 toolchain was updated by crrev.com/1502563003.

The VS 2015 toolchain used by v8 is also out of date. It is the wrong
compiler version (RTM instead of Update 1), the wrong SDK version, and
it is missing files such as the UCRT installers.

LOG=N
BUG=440500,491424

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

[commit-bot: I haz the power, 2016-01-27 18:18:14]

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