Make remoting_unittests build on Win64

Make remoting_unittests build on Win64 

Two simple compilation fixes and some c4267 build suppressions. 

BUG=166496
BUG=167187
R=wez@chromium.org
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=181650

[jschuh, 2013-02-10 00:01:41]

Minor fixes for win64.

[Wez, 2013-02-10 06:50:41]

LGTM

[commit-bot: I haz the power, 2013-02-10 13:55:19]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/jschuh@chromium.org/12225111/4001

[commit-bot: I haz the power, 2013-02-10 16:05:03]

Retried try job too often on win_rel for step(s) content_browsertests
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win_rel&nu...

[alexeypa (please no reviews), 2013-02-11 17:12:14]

Have you guys considered enabling /Wp64
(http://msdn.microsoft.com/en-us/library/yt4xw8fh(v=vs.100).aspx) on targets
that are free from C4267 warnings? This will make sure that x86 build will fail
if a new C4267 warning will be introduced in such a target.

[alexeypa (please no reviews), 2013-02-11 17:20:53]

On 2013/02/11 17:12:14, alexeypa wrote:
> Have you guys considered enabling /Wp64
> (http://msdn.microsoft.com/en-us/library/yt4xw8fh%28v=vs.100%29.aspx) on
targets
> that are free from C4267 warnings? This will make sure that x86 build will
fail
> if a new C4267 warning will be introduced in such a target.

Maybe it is not such a great idea. I tried it on targets in src/remoting and
got:

> cl : Command line warning D9035 : option 'Wp64' has been deprecated and will
be removed in a future release
> d:\src\chrome\src\third_party\platformsdk_win8\files\include\um\winnt.h(8037)
: error C2220: warning treated as error - no 'object' file generated
> d:\src\chrome\src\third_party\platformsdk_win8\files\include\um\winnt.h(8037)
: warning C4312: 'type cast' : conversion from 'LONG' to 'PVOID' of greater size
> ...

So not only the option is deprecated, but Win 8 SDK gives the size warning. :(

[jschuh, 2013-02-11 17:31:01]

On 2013/02/11 17:20:53, alexeypa wrote:
> On 2013/02/11 17:12:14, alexeypa wrote:
> > Have you guys considered enabling /Wp64
> > (http://msdn.microsoft.com/en-us/library/yt4xw8fh%2528v=vs.100%2529.aspx) on
> targets
> > that are free from C4267 warnings? This will make sure that x86 build will
> fail
> > if a new C4267 warning will be introduced in such a target.
> 
> Maybe it is not such a great idea. I tried it on targets in src/remoting and
> got:
> 
> > cl : Command line warning D9035 : option 'Wp64' has been deprecated and will
> be removed in a future release
> >
d:\src\chrome\src\third_party\platformsdk_win8\files\include\um\winnt.h(8037)
> : error C2220: warning treated as error - no 'object' file generated
> >
d:\src\chrome\src\third_party\platformsdk_win8\files\include\um\winnt.h(8037)
> : warning C4312: 'type cast' : conversion from 'LONG' to 'PVOID' of greater
size
> > ...
> 
> So not only the option is deprecated, but Win 8 SDK gives the size warning. :(

The windows build treats warnings as errors, so we're already getting that
behavior. That's why we're suppressing the warnings for now, but as narrowly as
we can. :)