#region TraviBlog

I remember when I used to change this tagline on a weekly basis

_AMD64_ for Win x64

I've been playing some MS webcasts on developing for Windows x64 (aka 64-bit Windows) in the background today and I just heard something kinda funny. The presenter just finished explaining that the compiler-time variable to test for the x64 version of Windows is:
#if define(_AMD64)
Then these questions followed:

Question: _AMD64_ is a definition for both AMD64 and EM64T Intel, right?
Answer: Yes. In the source code and header files _AMD64 applies to X64 as well.
Question: Will _AMD64_ be changed to _X64_? Will the Visual Studio 2005 platform "Win64 (AMD64)" be renamed?
Answer: At present there are no plans to make these changes.

He explained how at the time of development Intel had no plans whatsoever to release a 64-bit processor, and by the time they did announce it, it was way too late to change the constant's name.

I can't imagine being an Intel developer, writing drivers or something along those lines, and having to use _AMD64_. Talk about rubbing their noses in it.

Disclaimer: Every PC I currently own runs on AMD hardware, and as of this post I own shares of AMD.

posted on Thursday, November 04, 2004 11:45 AM

Feedback

# re: What's In A Name? 11/18/2004 1:19 PM Kernel Mustard

Leave Comments
if you can read this, your browser sucks.
upgrade:
*firefox* | mozilla | netscape | safari

#endregion