Mention -fms-compatibility and -fdelayed-template-parsing in UsersManual.

Also mention that -std=c++11 is now on by default on windows.



git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@160054 91177308-0d34-0410-b5e6-96231b3b80d8

1 files changed, 12 insertions, 0 deletions

diff --git a/docs/UsersManual.html b/docs/UsersManual.html
index 6a620d2018..0ca0e5377f 100644
--- a/docs/UsersManual.html
+++ b/docs/UsersManual.html
@@ -1082,6 +1082,14 @@ support is incomplete; enabling Microsoft extensions will silently drop
 certain constructs (including __declspec and Microsoft-style asm statements).
 </p>
 
+<p>clang has a -fms-compatibility flag that makes clang accept enough
+invalid C++ to be able to parse most Microsoft headers. This flag is enabled by
+default for Windows targets.</p>
+
+<p>-fdelayed-template-parsing lets clang delay all template instantiation until
+the end of a translation unit. This flag is enabled by default for Windows
+targets.</p>
+
 <ul>
 <li>clang allows setting _MSC_VER with -fmsc-version=. It defaults to 1300 which
 is the same as Visual C/C++ 2003. Any number is supported and can greatly affect
@@ -1096,6 +1104,8 @@ record members can be declared using user defined typedefs.</li>
 controlling record layout. GCC also contains support for this feature,
 however where MSVC and GCC are incompatible clang follows the MSVC
 definition.</li>
+
+<li>clang defaults to C++11 for Windows targets.</li>
 </ul>
 
 <!-- ======================================================================= -->
@@ -1181,6 +1191,8 @@ Generating assembly requires a suitable LLVM backend.
 
 <p>Experimental supports are on Cygming.</p>
 
+<p>See also <a href="#c_ms">Microsoft Extensions</a>.</p>
+
 <h5>Cygwin</h5>
 
 <p>Clang works on Cygwin-1.7.</p>