Repo sync for protected CLA branch

docs/assembler/inline/masm-macro-directives-in-inline-assembly.md

@@ -9,10 +9,10 @@ ms.assetid: 83643a09-1699-40a8-8ef2-13502bc4ac2c
 
 **Microsoft Specific**
 
-The inline assembler is not a macro assembler. You cannot use MASM macro directives (**MACRO**, `REPT`, **IRC**, `IRP`, and `ENDM`) or macro operators (**<>**, **!**, **&**, `%`, and `.TYPE`). An **`__asm`** block can use C preprocessor directives, however. See [Using C or C++ in __asm Blocks](../../assembler/inline/using-c-or-cpp-in-asm-blocks.md) for more information.
+The inline assembler isn't a macro assembler. You can't use MASM macro directives (`MACRO`, `REPT`, `IRC`, `IRP`, and `ENDM`) or macro operators (**`<>`**, **`!`**, **`&`**, **`%`**, and `.TYPE`). An **`__asm`** block can use C preprocessor directives, however. See [Using C or C++ in `__asm` blocks](../../assembler/inline/using-c-or-cpp-in-asm-blocks.md) for more information.
 
 **END Microsoft Specific**
 
 ## See also
 
-[Using Assembly Language in __asm Blocks](../../assembler/inline/using-assembly-language-in-asm-blocks.md)<br/>
+[Using assembly language in `__asm` blocks](../../assembler/inline/using-assembly-language-in-asm-blocks.md)

docs/assembler/inline/writing-functions-with-inline-assembly.md

@@ -1,39 +1,46 @@
 ---
-description: "Learn more about: Writing Functions with Inline Assembly"
-title: "Writing Functions with Inline Assembly"
-ms.date: "08/30/2018"
+description: "Learn more about: Writing functions with inline assembly"
+title: "Writing functions with inline assembly"
+ms.date: 02/11/2022
 helpviewer_keywords: ["functions [C++], inline assembly", "inline assembly [C++], writing functions", "assembler [C++], writing functions", "__asm keyword [C++], in functions"]
 ms.assetid: b5df8a04-fdc7-4622-8c9e-e4b618927497
 ---
-# Writing Functions with Inline Assembly
+# Writing functions with inline assembly
 
 **Microsoft Specific**
 
-If you write a function with inline assembly code, it's easy to pass arguments to the function and return a value from it. The following examples compare a function first written for a separate assembler and then rewritten for the inline assembler. The function, called `power2`, receives two parameters, multiplying the first parameter by 2 to the power of the second parameter. Written for a separate assembler, the function might look like this:
+> [!NOTE]
+> Inline assembly is only available for x86 targets. For similar functionality in x64 or ARM64 code, use [compiler intrinsics](../../intrinsics/compiler-intrinsics.md).
+
+If you write a function with inline assembly code, it's easy to pass arguments to the function and return a value from it. The following examples compare a function first written for a separate assembler and then rewritten for the inline assembler. The function, called `power2`, receives two parameters, multiplying the first parameter by 2 to the power of the second parameter. As a separate assembler file, the function might look like this:
 
 ```asm
-; POWER.ASM
-; Compute the power of an integer
-;
-       PUBLIC _power2
-_TEXT SEGMENT WORD PUBLIC 'CODE'
+; power2.asm 
+; x86 code for C interop
+; Command line: ml /c /Cx /W3 /WX power2.asm 
+        .686P
+        .XMM
+        .MODEL  flat
+
+PUBLIC  _power2
+; int power2(int num, int power);
+; computes num x 2^power
+_TEXT   SEGMENT
 _power2 PROC
-
-        push ebp        ; Save EBP
-        mov ebp, esp    ; Move ESP into EBP so we can refer
-                        ;   to arguments on the stack
-        mov eax, [ebp+4] ; Get first argument
-        mov ecx, [ebp+6] ; Get second argument
-        shl eax, cl     ; EAX = EAX * ( 2 ^ CL )
-        pop ebp         ; Restore EBP
-        ret             ; Return with sum in EAX
-
+        push    ebp             ; save EBP
+        mov     ebp, esp        ; Move ESP into EBP so we can refer
+                                ;   to arguments on the stack
+        mov     eax, [ebp+8]    ; load first argument
+        mov     ecx, [ebp+12]   ; load second argument
+        shl     eax, cl         ; compute result in EAX
+        pop     ebp             ; restore EBP
+        ret
 _power2 ENDP
 _TEXT   ENDS
-        END
+END
 ```
 
-Since it's written for a separate assembler, the function requires a separate source file and assembly and link steps. C and C++ function arguments are usually passed on the stack, so this version of the `power2` function accesses its arguments by their positions on the stack. (Note that the **MODEL** directive, available in MASM and some other assemblers, also allows you to access stack arguments and local stack variables by name.)
+Since it's written as a separate assembler file, the function requires separate assembly and link steps. C and C++ function arguments are usually passed on the stack, so this version of the `power2` function accesses its arguments by their positions on the stack. (The **`MODEL`** directive, available in MASM and some other assemblers, also allows you to access stack arguments and local stack variables by name.)
 
 ## Example
 
@@ -67,10 +74,10 @@ int power2( int num, int power )
 
 The inline version of the `power2` function refers to its arguments by name and appears in the same source file as the rest of the program. This version also requires fewer assembly instructions.
 
-Because the inline version of `power2` doesn't execute a C **`return`** statement, it causes a harmless warning if you compile at warning level 2 or higher. The function does return a value, but the compiler cannot tell that in the absence of a **`return`** statement. You can use [#pragma warning](../../preprocessor/warning.md) to disable the generation of this warning.
+Because the inline version of `power2` doesn't execute a C **`return`** statement, it causes a harmless warning if you compile at warning level 2 or higher. The function does return a value, but the compiler can't tell it does in the absence of a **`return`** statement. You can use [`#pragma warning`](../../preprocessor/warning.md) to disable the generation of this warning.
 
 **END Microsoft Specific**
 
 ## See also
 
-[Using C or C++ in __asm Blocks](../../assembler/inline/using-c-or-cpp-in-asm-blocks.md)<br/>
+[Using C or C++ in `__asm` Blocks](../../assembler/inline/using-c-or-cpp-in-asm-blocks.md)

docs/build/cmake-projects-in-visual-studio.md

@@ -1,7 +1,7 @@
 ---
 title: "CMake projects in Visual Studio"
 description: "How to create and build C++ projects using CMake in Visual Studio."
-ms.date: 12/15/2021
+ms.date: 02/14/2022
 helpviewer_keywords: ["CMake in Visual C++"]
 ms.assetid: 444d50df-215e-4d31-933a-b41841f186f8
 ---
@@ -41,9 +41,9 @@ When you **open a folder** containing a *`CMakeLists.txt`* file, the following t
 > [!NOTE]
 > Starting in Visual Studio 2022 version 17.1 Preview 2, if your folder doesn't contain a root `CMakeLists.txt` you'll be prompted whether you'd like to enable CMake integration or not. For more information, see [CMake partial activation](#cmake-partial-activation).
 
-Once CMake cache generation has succeeded, you can also view your projects organized logically by targets. Choose **Targets view** from the dropdown in the **Solution Explorer** toolbar:
+Once CMake cache generation has succeeded, you can also view your projects organized logically by targets. Choose the **Select View** button on the **Solution Explorer** toolbar. From the list in **Solution Explorer - Views**, select **CMake Targets View** and press **Enter** to open the targets view:
 
-![CMake targets view button.](media/cmake-targets-view.png)
+:::image type="content" source="media/cmake-targets-view2.png" alt-text="Screenshot of the Solution Explorer Views window with the C Make Targets View highlighted.":::
 
 Choose the **Show All Files** button at the top of **Solution Explorer** to see all the CMake-generated output in the *`out/build/<config>`* folders.
 
@@ -90,7 +90,7 @@ You can also disable all CMake cache notifications (gold bars) by deselecting **
 
 If you need more information about the state of the CMake cache to diagnose a problem, open the **Project** main menu or the *`CMakeLists.txt`* context menu in **Solution Explorer** to run one of these commands:
 
-- **View CMakeCache.txt** opens the *`CMakeCache.txt`* file from the build directory in the editor. Any edits you make here to *`CMakeCache.txt`* are wiped out if you clean the cache. To make changes that persist after you clean the cache, see [Customize CMake settings](customize-cmake-settings.md) or [Configure and Build with CMake Presets](cmake-presets-vs.md).
+- **View CMakeCache.txt** opens the *`CMakeCache.txt`* file from the build directory in the editor. Any edits you make here to *`CMakeCache.txt`* are wiped out if you clean the cache. To make changes that persist after you clean the cache, see [Customize CMake settings](customize-cmake-settings.md) or [Configure and build with CMake Presets](cmake-presets-vs.md).
 
 - **Delete Cache and Reconfigure** deletes the build directory and reconfigures from a clean cache.
 
@@ -149,7 +149,7 @@ Visual Studio allows you to debug a process running on a remote Linux system or
 
 ## <a name="cmake-partial-activation"></a> CMake partial activation
 
-Starting in Visual Studio 2022 version 17.1 Preview 2, CMake functionality won't be enabled automatically if your root folder doesn't contain a `CMakeLists.txt` file. Instead, a dialog will prompt you on whether you'd like to enable CMake functionality for your project. If you decline, CMake cache generation won't start and CMake configurations (from `CMakeSettings.json` or `CMakePresets.json`) won't appear in the configuration dropdown. If you accept, you'll be taken to a workspace-level configuration file, `CMakeWorkspaceSettings.json` (stored in the `.vs` directory), to specify the folders you'd like to enable CMake for. (These folders contain your root `CMakeLists.txt` files).
+In Visual Studio 2022 version 17.1 and later, CMake functionality won't be enabled automatically if your root folder doesn't contain a `CMakeLists.txt` file. Instead, a dialog will prompt you on whether you'd like to enable CMake functionality for your project. If you decline, CMake cache generation won't start and CMake configurations (from `CMakeSettings.json` or `CMakePresets.json`) won't appear in the configuration dropdown. If you accept, you'll be taken to a workspace-level configuration file, `CMakeWorkspaceSettings.json` (stored in the `.vs` directory), to specify the folders you'd like to enable CMake for. (These folders contain your root `CMakeLists.txt` files).
 
 The accepted properties are:
 
@@ -197,7 +197,7 @@ As soon as you save the file, the configuration step automatically runs again an
 
 ### Language services for CMake
 
-Language services for CMake are available in Visual Studio 2019 version 16.5 or later. Code navigation features like Go To Definition, Peek Definition, and Find All References are supported for CMake variables, functions, and targets in CMake script files. For more information, see [Code Navigation for CMake Scripts](https://devblogs.microsoft.com/cppblog/code-navigation-for-cmake-scripts/).
+Language services for CMake are available in Visual Studio 2019 version 16.5 or later. It supports code navigation features like Go To Definition, Peek Definition, and Find All References for CMake variables, functions, and targets in CMake script files. For more information, see [Code Navigation for CMake Scripts](https://devblogs.microsoft.com/cppblog/code-navigation-for-cmake-scripts/).
 
 ![Find All References on a CMake variable, target, or function.](media/cmake-find-all-refs.png)