On the large number of ways of expressing Microsoft Visual C++ compiler versions
When you ask someone what version of the Microsoft Visual C++ compiler they’re using, or if somebody tells you “This feature requires version X of the Microsoft Visual C++ compiler”, you can get the answer is a large number of ways, because the Microsoft Visual C++ compiler has apparently decided that if one version number is good, then more must be better.
The first version number that enters the picture is the name of the Visual Studio product the compiler comes with. This is probably something like “Visual Studio YYYY” for some year, like “Visual Studio 2019”.
The next version number is the product version of that Visual Studio product. For example, “Visual Studio 2019 version 16.11.”
The next version number is the platform toolset that you specify in your project file, like
Another version number is the actual toolchain version, like “14.29”.
And then there’s the version number reported by the
_MSC_VER predefined macro, like “1929”.
On top of that is the version number reported by the
_MSC_FULL_VER predefined macro, like “192930100”.
And finally, there’s the version number reported by the compiler itself when you type
How are all of these version numbers related?
Okay, let’s do the easy one first: The last three version numbers are related to each other in a straightforward way. If the compiler’s self-reported version is
aa.bb.ccccc.dd, then the
aabb and the
aabbccccc. In other words,
_MSC_VER = aa * 100 + bb and
_MSC_FULL_VER = aa * 10000000 + bb * 100000 + cc .
Okay, so that lets us build a relationship among the last three boxes: The compiler banner is the basis for the other two.
The first two boxes are also related, but in a less obvious way: The product name and product major version line up according to this table on Wikipedia. For example, Visual Studio 2019 corresponds to product versions 16.*.
The next two boxes also appear to be related, although I can’t find any official documentation to that effect. The platform toolset appears to be the letter “v”, followed by the toolchain major version, followed by the first digit of the minor version. For example, a toolchain version of “14.29” corresponds to a platform toolset of “v142”.
That leaves three major categories: The Visual Studio product, the toolchain, and the compiler. These three categories follow their own path, so you have to use a cheat sheet to see how they correspond to each other.¹
But wait, the story isn’t over yet.
Internally, the compiler team delivers periodic compiler updates to the Windows team. These updates are named LKG followed by a number, like “LKG14”, and there is an internal Web site that maps LKG values to compiler version numbers. Fortunately, only people who work at Microsoft need to worry about these LKG version numbers.
Bonus chatter: The term LKG stands for “Last Known Good”, meaning that it is the latest version of the compiler that has been validated against the Windows code base. There is another term FKG, which you think might stand for “First Known Good”, but it doesn’t. It originally stood for “Fast Known Good” because it contained compilers even newer than the Last Known Good. That policy has changed, and now the FKG is used for other purposes, but the name FKG stuck, even though it’s completely wrong.
¹ It appears that starting in Visual Studio 2017, the compiler minor version increases by one each time the toolchain minor version increases by one, so that’s handy. Starting in August 2017, the compiler version is equal to the toolchain version plus five. I don’t know whether this is a rule or a coincidence.