Merge pull request #5604 from MicrosoftDocs/main

6/24/2024 AM Publish

Author: Albertyang0

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

@@ -134,11 +134,11 @@ You can customize a CMake debugging session by setting properties in the *`launc
 
 ### Just My Code for CMake projects
 
-When you build for Windows using the MSVC compiler, CMake projects have support for Just My Code debugging. To change the Just My Code setting, go to **Tools** > **Options** > **Debugging** > **General**.
+When you build for Windows using the MSVC compiler, CMake projects have support for Just My Code debugging. To change the Just My Code setting, go to **Tools** > **Options** > **Debugging** > **General**. For more information on Just My Code debugging, see [Debug only user code with Just My Code](/visualstudio/debugger/just-my-code).
 
 ### Edit and Continue for CMake projects
 
-When you build for Windows with the MSVC compiler, CMake projects have support for Edit and Continue. Add the following code to your *`CMakeLists.txt`* file to enable Edit and Continue.
+When you build for Windows with the MSVC compiler, CMake projects have support for Edit and Continue. Add the following code to your *`CMakeLists.txt`* file to enable Edit and Continue. For more information on Edit and Continue, see [Configure Edit and Continue (C#, VB, C++)](/visualstudio/debugger/how-to-enable-and-disable-edit-and-continue).
 
 ```
 if(MSVC)
@@ -432,4 +432,4 @@ In Visual Studio 2015, Visual Studio users can use a [CMake generator](https://c
 [Deploy, run, and debug your Linux project](../linux/deploy-run-and-debug-your-linux-project.md)\
 [CMake predefined configuration reference](cmake-predefined-configuration-reference.md)\
 [vcpkg in CMake projects](/vcpkg/users/buildsystems/cmake-integration)\
-[Install and use packages with CMake in Visual Studio](/vcpkg/get_started/get-started-vs)
+[Install and use packages with CMake in Visual Studio](/vcpkg/get_started/get-started-vs)

docs/build/x64-software-conventions.md

@@ -18,6 +18,8 @@ Given the expanded register set, x64 uses the [__fastcall](../cpp/fastcall.md) c
 
 The **`__fastcall`** convention uses registers for the first four arguments, and the stack frame to pass more arguments. For details on the x64 calling convention, including register usage, stack parameters, return values, and stack unwinding, see [x64 calling convention](x64-calling-convention.md).
 
+For more information on the `__vectorcall` calling convention, see [`__vectorcall`](../cpp/vectorcall.md).
+
 ## Enable x64 compiler optimization
 
 The following compiler option helps you optimize your application for x64:

docs/intrinsics/arm64-intrinsics.md

@@ -15,10 +15,12 @@ The Microsoft C++ compiler (MSVC) makes the following intrinsics available on th
 
 The NEON vector instruction set extensions for ARM64 provide Single Instruction Multiple Data (SIMD) capabilities. They resemble the ones in the MMX and SSE vector instruction sets that are common to x86 and x64 architecture processors.
 
-NEON intrinsics are supported, as provided in the header file *arm64_neon.h*. The MSVC support for NEON intrinsics resembles that of the ARM64 compiler, which is documented in the [ARM NEON Intrinsic Reference](https://developer.arm.com/architectures/instruction-sets/simd-isas/neon/intrinsics) on the ARM Infocenter website.
+NEON intrinsics are supported, as provided in the header file `arm64_neon.h`. The MSVC support for NEON intrinsics resembles that of the ARM64 compiler, which is documented in the [ARM NEON Intrinsic Reference](https://developer.arm.com/architectures/instruction-sets/simd-isas/neon/intrinsics) on the ARM Infocenter website.
 
 ## <a name="A"></a> ARM64-specific intrinsics listing
 
+ARM64-specific intrinsics are supported, as provided in the header file `intrin.h`.
+
 |Function Name|Instruction|Function Prototype|
 |-------------------|-----------------|------------------------|
 |__break|BRK|void __break(int)|