hmm, that wont be needed... I guess
, i mean, all you need is stuff like :
Microsoft Platform SDK for Windows Server 2003 SP1 and
microsof Visual Studion 2005 (the compiler must be able to compile 64bits instructions), he wont need a 64 bits cpu.. why?? well he just compilese it as 64bits, and sends it out to a few beta testers first like 5 -10, if it works, he can get some more people test it out, and voila messenger plus! 64bits is born
heck 32bits hardware can compile it as far as i could read it
quote:
Go Ahead and Port
More Exciting Porting and Portability Tips
When it's time to compile, use the /Wp64 switch with the Microsoft Visual C/C++ compiler; it's available on the 32-bit compiler, and using it is one of the first steps to porting. With that switch thrown, the compiler will warn you about portability issues—pay attention to those messages, since you want to get your code "64-bit clean." (If you're working with the "Whidbey" version of Visual Studio .NET, please note that it includes native support for compiling to AMD64 Windows platforms!)
Post compilation, be sure to test, test, test. You may find additional bugs in your code, especially when implicit conversions don't go as you'd expect. Be careful to keep synchronization between C and assembly data structures, and pay attention to the new data types, data sizes and alignments.
Finally, use benchmarking to help identify parts of your code that need extra attention after the port. The ideal tool is AMD CodeAnalyst , which you can download free of charge. DevX has written an article about it—see "Getting In Touch With Your Inner Code."
Mike Wall is a Senior Member of Technical Staff in the Developer Performance Team at Advanced Micro Devices Inc.
source:
http://www.devx.com/amd/Article/17783/2907?pf=true
subject: Tricks for porting applications to 64-bit Windows om AMD64 architecture...
