[clang-cl] document correct defaults for -fms-compatibility-version / -fmsc-version (#76418)

The UserManual states wrongly (AFAICT) that these default are not being
defined for clang-cl, whereas further up the opposite is stated:


c86fe3ee0b/clang/docs/UsersManual.rst (L3375-L3382)

I've chosen to follow that wording, as it's the latest related update.

CC @RIscRIpt who recently touched this in
b3e6ff3319
CC @AaronBallman who cared about this, c.f.
8fc0dcf036
This commit is contained in:
h-vetinari 2024-01-17 15:28:29 +11:00 committed by GitHub
parent 0a64367a72
commit 3e0d71cdf4
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 3 additions and 3 deletions

View File

@ -302,7 +302,7 @@ Language Selection and Mode Options
.. option:: -fmsc-version=
Set ``_MSC_VER``. When on Windows, this defaults to either the same value as
the currently installed version of cl.exe, or ``1920``. Not set otherwise.
the currently installed version of cl.exe, or ``1933``. Not set otherwise.
.. option:: -fborland-extensions

View File

@ -4436,11 +4436,11 @@ Execute ``clang-cl /?`` to see a list of supported options:
-fmerge-all-constants Allow merging of constants
-fms-compatibility-version=<value>
Dot-separated value representing the Microsoft compiler version
number to report in _MSC_VER (0 = don't define it (default))
number to report in _MSC_VER (0 = don't define it; default is same value as installed cl.exe, or 1933)
-fms-compatibility Enable full Microsoft Visual C++ compatibility
-fms-extensions Accept some non-standard constructs supported by the Microsoft compiler
-fmsc-version=<value> Microsoft compiler version number to report in _MSC_VER
(0 = don't define it (default))
(0 = don't define it; default is same value as installed cl.exe, or 1933)
-fno-addrsig Don't emit an address-significance table
-fno-builtin-<value> Disable implicit builtin knowledge of a specific function
-fno-builtin Disable implicit builtin knowledge of functions