From be7e33426d4e260b717c38784af7beda71043ff5 Mon Sep 17 00:00:00 2001 From: Nico Weber Date: Wed, 5 Mar 2014 20:18:59 +0000 Subject: [PATCH] Mention clang-cl in MSVCCompatibility.rst git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@203002 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/MSVCCompatibility.rst | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/MSVCCompatibility.rst b/docs/MSVCCompatibility.rst index 879bb3de16..683ce937b4 100644 --- a/docs/MSVCCompatibility.rst +++ b/docs/MSVCCompatibility.rst @@ -28,13 +28,16 @@ Second, Clang implements many MSVC language extensions, such as ``__declspec(dllexport)`` and a handful of pragmas. These are typically controlled by ``-fms-extensions``. -Finally, MSVC accepts some C++ code that Clang will typically diagnose as +Third, MSVC accepts some C++ code that Clang will typically diagnose as invalid. When these constructs are present in widely included system headers, Clang attempts to recover and continue compiling the user's program. Most parsing and semantic compatibility tweaks are controlled by ``-fms-compatibility`` and ``-fdelayed-template-parsing``, and they are a work in progress. +Finally, there is :ref:`clang-cl`, a driver program for clang that attempts to +be compatible with MSVC's cl.exe. + ABI features ============ -- 2.50.1