What's the error you're trying to fix? Although these messages use size_t, the size of which is platform-specific, we always serialize it as a 64-bit integer and check that it fits in the platform-specific size. Josh added that code. (I'm not necessarily against changing the messages here, I just want to make sure you're not spending time that could better be used elsewhere.)

(In reply to comment #2) > What's the error you're trying to fix? Although these messages use size_t, > the size of which is platform-specific, we always serialize it as a 64-bit > integer and check that it fits in the platform-specific size. Josh added > that code. (I'm not necessarily against changing the messages here, I just > want to make sure you're not spending time that could better be used > elsewhere.) Before fixing bug 620888. size_t was compatible both x86 and x64. But, before fixing it, ReadParam(uint32) wasn't compatible on MSVC.

Also should I backout bug 620888, then should I add fix to extract ReadParam(uint32) to ReadParam(uint64) on Win64 platform? If backouting bug 620888 on Win32, ReadParam(uint32) becomes readParam(intptr_t) on IPC.