Is this another one of the endless bugs caused by Microsoft choosing a different ABI for amd64/x86-64/x64 than the unix ABI for amd64/x86-64/x64?