msvs_emulation: Add support for StackReserveSize and StackCommitSize

msvs_emulation: Add support for StackReserveSize and StackCommitSize

Note that StackCommitSize has no effect unless StackReserveSize is also set.
This is consistent with how msvs works.

BUG=
R=scottmg@chromium.org

Committed: https://chromium.googlesource.com/external/gyp/+/010fb9d696e7c79ffcbc4342efff3436cdc19f90

[Shezan Baig (Bloomberg), 2015-08-13 08:30:47]

sbaig1@bloomberg.net changed reviewers:
+ scottmg@chromium.org

[Shezan Baig (Bloomberg), 2015-08-13 08:42:07]

Hmm, I tried "git cl try" but the trybots show up grey

[Shezan Baig (Bloomberg), 2015-08-13 08:47:49]

The CQ bit was checked by sbaig1@bloomberg.net to run a CQ dry run

[Shezan Baig (Bloomberg), 2015-08-13 08:48:55]

On 2015/08/13 08:42:07, Shezan Baig (Bloomberg) wrote:
> Hmm, I tried "git cl try" but the trybots show up grey

"CQ dry run" seems to work :)

[commit-bot: I haz the power, 2015-08-13 08:50:01]

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

[commit-bot: I haz the power, 2015-08-13 08:50:02]

Commit queue rejected this change because it did not recognize the base URL.
Please commit your change manually.

[scottmg, 2015-08-13 16:16:55]

lgtm

[Dirk Pranke, 2015-08-13 17:11:54]

On 2015/08/13 08:48:55, Shezan Baig (Bloomberg) wrote:
> On 2015/08/13 08:42:07, Shezan Baig (Bloomberg) wrote:
> > Hmm, I tried "git cl try" but the trybots show up grey
> 
> "CQ dry run" seems to work :)

From what I can see, "CQ dry run" either didn't do anything, or also just
triggered a set of jobs that got scheduled but didn't actually run. 

Further, I would not expect the CQ to work; we don't have a configured CQ for
GYP. 

I'm not sure why the try jobs aren't running. I will take a look.

[Shezan Baig (Bloomberg), 2015-08-13 17:17:25]

On 2015/08/13 17:11:54, Dirk Pranke wrote:
> On 2015/08/13 08:48:55, Shezan Baig (Bloomberg) wrote:
> > On 2015/08/13 08:42:07, Shezan Baig (Bloomberg) wrote:
> > > Hmm, I tried "git cl try" but the trybots show up grey
> > 
> > "CQ dry run" seems to work :)
> 
> From what I can see, "CQ dry run" either didn't do anything, or also just
> triggered a set of jobs that got scheduled but didn't actually run. 
> 


Yeah, I spoke to soon :)  It looked like it was doing something, then it error'd
out.


> Further, I would not expect the CQ to work; we don't have a configured CQ for
> GYP. 
> 
> I'm not sure why the try jobs aren't running. I will take a look.


Thanks!

[Shezan Baig (Bloomberg), 2015-08-14 08:52:02]

Committed patchset #2 (id:20001) manually as
010fb9d696e7c79ffcbc4342efff3436cdc19f90 (presubmit successful).