However, I would think that if *nix builds generated as many warnings as the x64 windows build, p5p would do something about it quicksmart.

True, but that's something else than

Given that the perl community (in general) frowns so heavily upon warnings being emitted at *any* stage, it's rather surprising that this sort of thing is tolerated.

Personally, I'm not greatly perturbed - the main problem on x64 windows is that, because there's so many warnings, your chances of spotting the odd one out that *does* have a bearing on a problem is greatly reduced.

Yes. To bad that six release candidates (RC0 - RC5) were made available over a period of several weeks, and noone spoke up about this issue then. One of the reasons Perl .0 releases have a bad reputation is that release candidates are commonly ignored - and problems are only spotted afterwards.