Merge pull request #811 from MicrosoftDocs/master

5/15 AM Publishing

Author: Saisang

docs/build/register-usage.md

@@ -1,5 +1,5 @@
 ---
-title: "Register Usage | Microsoft Docs"
+title: "Register usage | Microsoft Docs"
 ms.custom: ""
 ms.date: "11/04/2016"
 ms.technology: ["cpp-tools"]
@@ -10,34 +10,41 @@ author: "corob-msft"
 ms.author: "corob"
 ms.workload: ["cplusplus"]
 ---
-# Register Usage
-The [!INCLUDE[vcprx64](../assembler/inline/includes/vcprx64_md.md)] architecture provides for 16 general-purpose registers (hereafter referred to as integer registers) as well as 16 XMM/YMM registers available for floating-point use. Volatile registers are scratch registers presumed by the caller to be destroyed across a call. Nonvolatile registers are required to retain their values across a function call and must be saved by the callee if used.  
-  
- The following table describes how each register is used across function calls:  
-  
-||||  
-|-|-|-|  
-|Register|Status|Use|  
-|RAX|Volatile|Return value register|  
-|RCX|Volatile|First integer argument|  
-|RDX|Volatile|Second integer argument|  
-|R8|Volatile|Third integer argument|  
-|R9|Volatile|Fourth integer argument|  
-|R10:R11|Volatile|Must be preserved as needed by caller; used in syscall/sysret instructions|  
-|R12:R15|Nonvolatile|Must be preserved by callee|  
-|RDI|Nonvolatile|Must be preserved by callee|  
-|RSI|Nonvolatile|Must be preserved by callee|  
-|RBX|Nonvolatile|Must be preserved by callee|  
-|RBP|Nonvolatile|May be used as a frame pointer; must be preserved by callee|  
-|RSP|Nonvolatile|Stack pointer|  
-|XMM0, YMM0|Volatile|First FP argument; first vector-type argument when `__vectorcall` is used|  
-|XMM1, YMM1|Volatile|Second FP argument; second vector-type argument when `__vectorcall` is used|  
-|XMM2, YMM2|Volatile|Third FP argument; third vector-type argument when `__vectorcall` is used|  
-|XMM3, YMM3|Volatile|Fourth FP argument; fourth vector-type argument when `__vectorcall` is used|  
-|XMM4, YMM4|Volatile|Must be preserved as needed by caller; fifth vector-type argument when `__vectorcall` is used|  
-|XMM5, YMM5|Volatile|Must be preserved as needed by caller; sixth vector-type argument when `__vectorcall` is used|  
-|XMM6:XMM15, YMM6:YMM15|Nonvolatile (XMM), Volatile (upper half of YMM)|Must be preserved by callee. YMM registers must be preserved as needed by caller.|  
-  
-## See Also  
- [x64 Software Conventions](../build/x64-software-conventions.md)   
- [__vectorcall](../cpp/vectorcall.md)
+# Register usage
+
+The x64 architecture provides for 16 general-purpose registers (hereafter referred to as integer registers) as well as 16 XMM/YMM registers available for floating-point use. Volatile registers are scratch registers presumed by the caller to be destroyed across a call. Nonvolatile registers are required to retain their values across a function call and must be saved by the callee if used.
+
+## Register volatility and preservation
+
+The following table describes how each register is used across function calls:
+
+||||
+|-|-|-|
+|Register|Status|Use|
+|RAX|Volatile|Return value register|
+|RCX|Volatile|First integer argument|
+|RDX|Volatile|Second integer argument|
+|R8|Volatile|Third integer argument|
+|R9|Volatile|Fourth integer argument|
+|R10:R11|Volatile|Must be preserved as needed by caller; used in syscall/sysret instructions|
+|R12:R15|Nonvolatile|Must be preserved by callee|
+|RDI|Nonvolatile|Must be preserved by callee|
+|RSI|Nonvolatile|Must be preserved by callee|
+|RBX|Nonvolatile|Must be preserved by callee|
+|RBP|Nonvolatile|May be used as a frame pointer; must be preserved by callee|
+|RSP|Nonvolatile|Stack pointer|
+|XMM0, YMM0|Volatile|First FP argument; first vector-type argument when `__vectorcall` is used|
+|XMM1, YMM1|Volatile|Second FP argument; second vector-type argument when `__vectorcall` is used|
+|XMM2, YMM2|Volatile|Third FP argument; third vector-type argument when `__vectorcall` is used|
+|XMM3, YMM3|Volatile|Fourth FP argument; fourth vector-type argument when `__vectorcall` is used|
+|XMM4, YMM4|Volatile|Must be preserved as needed by caller; fifth vector-type argument when `__vectorcall` is used|
+|XMM5, YMM5|Volatile|Must be preserved as needed by caller; sixth vector-type argument when `__vectorcall` is used|
+|XMM6:XMM15, YMM6:YMM15|Nonvolatile (XMM), Volatile (upper half of YMM)|Must be preserved by callee. YMM registers must be preserved as needed by caller.|
+
+On function exit and on function entry to C Runtime Library calls and Windows system calls, the direction flag in the CPU flags register is expected to be cleared.
+
+## See also
+
+- [x64 Software Conventions](../build/x64-software-conventions.md)
+- [__vectorcall](../cpp/vectorcall.md)
+- [Direction flag](../c-runtime-library/direction-flag.md)

docs/c-runtime-library/reference/localtime-s-localtime32-s-localtime64-s.md

@@ -23,16 +23,16 @@ Converts a **time_t** time value to a **tm** structure, and corrects for the loc
 
 ```C
 errno_t localtime_s(
-   struct tm* tmDest,
-   const time_t *sourceTime
+   struct tm* const tmDest,
+   time_t const* const sourceTime
 );
 errno_t _localtime32_s(
    struct tm* tmDest,
-   const time32_t *sourceTime
+   __time32_t const* sourceTime
 );
 errno_t _localtime64_s(
    struct tm* tmDest,
-   const _time64_t *sourceTime
+   __time64_t const* sourceTime
 );
 ```
 

docs/error-messages/compiler-errors-1/compiler-error-c2482.md

@@ -14,20 +14,25 @@ ms.workload: ["cplusplus"]
 ---
 # Compiler Error C2482
 
->'*identifier*' : dynamic initialization of 'thread' data not allowed
+>'*identifier*' : dynamic initialization of 'thread' data not allowed in managed/WinRT code
 
-This error message is obsolete in Visual Studio 2015 and later versions. In previous versions, variables declared by using the `thread` attribute cannot be initialized with an expression that requires run-time evaluation. A static expression is required to initialize `thread` data.
+## Remarks
+
+In managed or WinRT code, variables declared by using the [__declspec(thread)](../../cpp/thread.md) storage class modifier attribute or the [thread_local](../../cpp/storage-classes-cpp.md#thread_local) storage class specifier cannot be initialized with an expression that requires evaluation at run-time. A static expression is required to initialize `__declspec(thread)` or `thread_local` data in these runtime environments.
 
 ## Example
 
-The following sample generates C2482 in Visual Studio 2013 and earlier:
+The following sample generates C2482 in managed (**/clr**) and in WinRT (**/ZW**) code:
 
 ```cpp
 // C2482.cpp
-// compile with: /c
+// For managed example, compile with: cl /EHsc /c /clr C2482.cpp
+// For WinRT example, compile with: cl /EHsc /c /ZW C2482.cpp
 #define Thread __declspec( thread )
-Thread int tls_i = tls_i;   // C2482
+Thread int tls_i1 = tls_i1;   // C2482
 
 int j = j;   // OK in C++; C error
-Thread int tls_i = sizeof( tls_i );   // Okay in C and C++
+Thread int tls_i2 = sizeof( tls_i2 );   // Okay in C and C++
 ```
+
+To fix this issue, initialize thread-local storage by using a constant, **constexpr**, or static expression. Perform any thread-specific initialization separately.

docs/error-messages/compiler-warnings/compiler-warning-level-1-c4067.md

@@ -13,35 +13,45 @@ ms.author: "corob"
 ms.workload: ["cplusplus"]
 ---
 # Compiler Warning (level 1) C4067
-unexpected tokens following preprocessor directive - expected a newline  
-  
- The compiler found and ignored extra characters following a preprocessor directive. This warning appears only under ANSI compatibility ([/Za](../../build/reference/za-ze-disable-language-extensions.md)).  
-  
-```  
-// C4067a.cpp  
-// compile with: /DX /Za /W1  
-#pragma warning(default:4067)  
-#if defined(X)  
-#else  
-#endif v   // C4067  
-int main()  
-{  
-}  
-```  
-  
-### To resolve this warning, try the following:  
-  
-1.  Compile with **/Ze**.  
-  
-2.  Use comment delimiters:  
-  
-```  
-// C4067b.cpp  
-// compile with: /DX /Za /W1  
-#if defined(X)  
-#else  
-#endif  
-int main()  
-{  
-}  
+
+> unexpected tokens following preprocessor directive - expected a newline
+
+## Remarks
+
+The compiler found and ignored extra characters following a preprocessor directive. This can be caused by any unexpected characters, though a common cause is a stray semicolon after the directive. Comments do not cause this warning. The **/Za** compiler option enables this warning for more preprocessor directives than the default setting.
+
+## Example
+
+```cpp
+// C4067a.cpp
+// compile with: cl /EHsc /DX /W1 /Za C4067a.cpp
+#include <iostream>
+#include <string> s     // C4067
+#if defined(X);         // C4067
+std::string s{"X is defined"};
+#else
+std::string s{"X is not defined"};
+#endif;                 // C4067 only under /Za
+int main()
+{
+    std::cout << s << std::endl;
+}
+```
+
+To resolve this warning, delete the stray characters, or move them into a comment block. Certain C4067 warnings may be disabled by removing the **/Za** compiler option.
+
+```cpp
+// C4067b.cpp
+// compile with: cl /EHsc /DX /W1 C4067b.cpp
+#include <iostream>
+#include <string>
+#if defined(X)
+std::string s{"X is defined"};
+#else
+std::string s{"X is not defined"};
+#endif
+int main()
+{
+    std::cout << s << std::endl;
+}
 ```

docs/error-messages/compiler-warnings/compiler-warning-level-1-c4503.md

@@ -1,7 +1,7 @@
 ---
 title: "Compiler Warning (level 1) C4503 | Microsoft Docs"
 ms.custom: ""
-ms.date: "11/04/2016"
+ms.date: "05/14/2018"
 ms.technology: ["cpp-diagnostics"]
 ms.topic: "error-reference"
 f1_keywords: ["C4503"]
@@ -13,56 +13,64 @@ ms.author: "corob"
 ms.workload: ["cplusplus"]
 ---
 # Compiler Warning (level 1) C4503
-'identifier' : decorated name length exceeded, name was truncated  
-  
- The decorated name was longer than the compiler limit (4096), and was truncated. To avoid this warning and the truncation, reduce the number of arguments or name length of identifiers used.  
-  
- One situation where this warning will be issued is when your code contains templates specialized on templates repeatedly.  For example, a map of maps (from the C++ Standard Library).  In this situation, you can make your typedefs a type (struct, for example) that contains the map.  
-  
- You might, however, decide to not restructure your code.  It is possible to ship an application that generates C4503, but if you get link time errors on a truncated symbol, it will be more difficult to determine the type of the symbol in the error.  Debugging will also be more difficult; the debugger will also have difficultly mapping symbol name to type name.  The correctness of the program, however, is unaffected by the truncated name.  
-  
- The following sample generates C4503:  
-  
-```  
-// C4503.cpp  
-// compile with: /W1 /EHsc /c  
-// C4503 expected  
-#include <string>  
-#include <map>  
-  
-class Field{};  
-  
-typedef std::map<std::string, Field> Screen;  
-typedef std::map<std::string, Screen> WebApp;  
-typedef std::map<std::string, WebApp> WebAppTest;  
-typedef std::map<std::string, WebAppTest> Hello;  
-Hello MyWAT;  
-```  
-  
- The following sample shows one way to rewrite your code to resolve C4503:  
-  
-```  
-// C4503b.cpp  
-// compile with: /W1 /EHsc /c  
-#include <string>  
-#include <map>  
-  
-class Field{};  
-struct Screen2 {  
-   std::map<std::string, Field> Element;  
-};  
-  
-struct WebApp2 {  
-   std::map<std::string, Screen2> Element;  
-};  
-  
-struct WebAppTest2 {  
-   std::map<std::string, WebApp2> Element;  
-};  
-  
-struct Hello2 {  
-   std::map<std::string, WebAppTest2> Element;  
-};  
-  
-Hello2 MyWAT2;  
+
+> '*identifier*' : decorated name length exceeded, name was truncated
+
+## Remarks
+
+This compiler warning is obsolete and is not generated in Visual Studio 2017 and later compilers.
+
+The decorated name was longer than the compiler limit (4096), and was truncated. To avoid this warning and the truncation, reduce the number of arguments or the name lengths of identifiers used. Decorated names that are longer than the compiler limit have a hash applied and are not in danger of a name collision.
+
+When using an older version of Visual Studio, this warning can be issued when your code contains templates specialized on templates repeatedly. For example, a map of maps (from the C++ Standard Library). In this situation, you can make your typedefs a type (a **struct**, for example) that contains the map.
+
+You might, however, decide to not restructure your code.  It is possible to ship an application that generates C4503, but if you get link time errors on a truncated symbol, it can be more difficult to determine the type of the symbol in the error. Debugging may also be more difficult; the debugger may have difficultly mapping the symbol name to the type name. The correctness of the program, however, is unaffected by the truncated name.
+
+## Example
+
+The following sample generates C4503 in compilers before Visual Studio 2017:
+
+```cpp
+// C4503.cpp
+// compile with: /W1 /EHsc /c
+// C4503 expected
+#include <string>
+#include <map>
+
+class Field{};
+
+typedef std::map<std::string, Field> Screen;
+typedef std::map<std::string, Screen> WebApp;
+typedef std::map<std::string, WebApp> WebAppTest;
+typedef std::map<std::string, WebAppTest> Hello;
+Hello MyWAT;
+```
+
+This sample shows one way to rewrite your code to resolve C4503:
+
+```cpp
+// C4503b.cpp
+// compile with: /W1 /EHsc /c
+#include <string>
+#include <map>
+
+class Field{};
+
+struct Screen2 {
+   std::map<std::string, Field> Element;
+};
+
+struct WebApp2 {
+   std::map<std::string, Screen2> Element;
+};
+
+struct WebAppTest2 {
+   std::map<std::string, WebApp2> Element;
+};
+
+struct Hello2 {
+   std::map<std::string, WebAppTest2> Element;
+};
+
+Hello2 MyWAT2;
 ```

docs/ide/TOC.md

@@ -71,6 +71,7 @@
 ## [Understanding the Dependencies of a Visual C++ Application](understanding-the-dependencies-of-a-visual-cpp-application.md)
 ## [Determining Which DLLs to Redistribute](determining-which-dlls-to-redistribute.md)
 ## [Choosing a Deployment Method](choosing-a-deployment-method.md)
+## [Universal CRT deployment](universal-crt-deployment.md)
 ## [Redistributing Visual C++ Files](redistributing-visual-cpp-files.md)
 ### [Redistributing Components By Using Merge Modules](redistributing-components-by-using-merge-modules.md)
 ### [Redistributing Visual C++ ActiveX Controls](redistributing-visual-cpp-activex-controls.md)