Merge pull request #5835 from MicrosoftDocs/FromPublicMasterBranch

Confirm merge from FromPublicMasterBranch to main to sync with https://github.com/MicrosoftDocs/cpp-docs (branch main)

Author: Albertyang0

docs/build/arm64-exception-handling.md

@@ -299,14 +299,20 @@ The unwind codes are encoded according to the table below. All unwind codes are
 | `save_fregp_x` | 1101101x'xxzzzzzz: save pair `d(8+#X)` at `[sp-(#Z+1)*8]!`, pre-indexed offset >= -512 |
 | `save_freg` | 1101110x'xxzzzzzz: save reg `d(8+#X)` at `[sp+#Z*8]`, offset \<= 504 |
 | `save_freg_x` | 11011110'xxxzzzzz: save reg `d(8+#X)` at `[sp-(#Z+1)*8]!`, pre-indexed offset >= -256 |
+| `alloc_z` | 11011111'zzzzzzzz: allocate stack with size `z * SVE-VL` |
 | `alloc_l` | 11100000'xxxxxxxx'xxxxxxxx'xxxxxxxx: allocate large stack with size \< 256M (2^24 * 16) |
 | `set_fp` | 11100001: set up `x29` with `mov x29,sp` |
 | `add_fp` | 11100010'xxxxxxxx: set up `x29` with `add x29,sp,#x*8` |
 | `nop` | 11100011: no unwind operation is required. |
 | `end` | 11100100: end of unwind code. Implies `ret` in epilog. |
 | `end_c` | 11100101: end of unwind code in current chained scope. |
-| `save_next` | 11100110: save next non-volatile Int or FP register pair. |
-|  | 11100111: reserved |
+| `save_next` | 11100110: save next register pair. |
+| `save_any_xreg` | 11100111'0pxrrrrr'00oooooo: save register(s)<ul><li>`p`: 0/1 => single `X(#r)` vs pair `X(#r)` + `X(#r+1)`</li><li>`x`: 0/1 => positive vs negative pre-indexed stack offset</li><li>`o`: offset = `o` * 16, if x=1 or p=1, else `o` * 8</li></ul>(Windows >= 11 required) |
+| `save_any_dreg` | 11100111'0pxrrrrr'01oooooo: save register(s)<ul><li>`p`: 0/1 => single `D(#r)` vs pair `D(#r)` + `D(#r+1)`</li><li>`x`: 0/1 => positive vs negative pre-indexed stack offset</li><li>`o`: offset = `o` * 16, if x=1 or p=1, else `o` * 8</li></ul>(Windows >= 11 required) |
+| `save_any_qreg` | 11100111'0pxrrrrr'10oooooo: save register(s)<ul><li>`p`: 0/1 => single `Q(#r)` vs pair `Q(#r)` + `Q(#r+1)`</li><li>`x`: 0/1 => positive vs negative pre-indexed stack offset</li><li>`o`: offset = `o` * 16</li></ul>(Windows >= 11 required) |
+| `save_zreg` | 11100111'0oo0rrrr'11oooooo: save reg `Z(#r+8)` at `[sp + #o * VL]`, (`Z8` through `Z23`)
+| `save_preg` | 11100111'0oo1rrrr'11oooooo: save reg `P(#r+8)` at `[sp + #o * (VL / 8)]`, (`P4` through `P15`; `r` values `[0, 3]` are reserved)
+|  | 11100111'1yyyyyyy': reserved |
 |  | 11101xxx: reserved for custom stack cases below only generated for asm routines |
 |  | 11101000: Custom stack for `MSFT_OP_TRAP_FRAME` |
 |  | 11101001: Custom stack for `MSFT_OP_MACHINE_FRAME` |
@@ -330,7 +336,7 @@ In instructions with large values covering multiple bytes, the most significant
 
 Post-indexed offset addressing isn't allowed in a prolog. All offset ranges (#Z) match the encoding of `stp`/`str` addressing except `save_r19r20_x`, in which 248 is sufficient for all save areas (10 Int registers + 8 FP registers + 8 input registers).
 
-`save_next` must follow a save for Int or FP volatile register pair: `save_regp`, `save_regp_x`, `save_fregp`, `save_fregp_x`, `save_r19r20_x`, or another `save_next`. It saves the next register pair at the next 16-byte slot in "growing up" order. A `save_next` refers to the first FP register pair when it follows the `save-next` that denotes the last Int register pair.
+`save_next` must follow a save for a register pair: `save_regp`, `save_regp_x`, `save_fregp`, `save_fregp_x`, `save_r19r20_x`, or another `save_next`. It can also be used in conjunction with `save_any_xreg`, `save_any_dreg` or `save_any_qreg` but only when `p = 1`. It saves the next register pair in numerically increasing order to the next stack space. `save_next` must not be used beyond the last register of the same kind.
 
 Since the sizes of regular return and jump instructions are the same, there's no need for a separated `end` unwind code in tail-call scenarios.
 

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

@@ -1,14 +1,13 @@
 ---
-description: "Learn more about: Compiler Error C2283"
 title: "Compiler Error C2283"
+description: "Learn more about: Compiler Error C2283"
 ms.date: "11/04/2016"
 f1_keywords: ["C2283"]
 helpviewer_keywords: ["C2283"]
-ms.assetid: 8a5b3175-b480-4598-a1f7-0b50504c5caa
 ---
 # Compiler Error C2283
 
-'identifier' : pure specifier or abstract override specifier not allowed on unnamed struct
+> '*identifier*': pure specifier or abstract override specifier not allowed on unnamed struct
 
 A member function of an unnamed class or structure is declared with a pure specifier, which is not permitted.
 

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

@@ -1,14 +1,13 @@
 ---
-description: "Learn more about: Compiler Error C2466"
 title: "Compiler Error C2466"
-ms.date: "11/04/2016"
+description: "Learn more about: Compiler Error C2466"
+ms.date: "03/19/2025"
 f1_keywords: ["C2466"]
 helpviewer_keywords: ["C2466"]
-ms.assetid: 75b251d1-7d0b-4a86-afca-26adedf74486
 ---
 # Compiler Error C2466
 
-cannot allocate an array of constant size 0
+> cannot allocate an array of constant size 0
 
 An array is allocated or declared with size zero. The constant expression for the array size must be an integer greater than zero. An array declaration with a zero subscript is legal only for a class, structure, or union member and only with Microsoft extensions ([/Ze](../../build/reference/za-ze-disable-language-extensions.md)).
 
@@ -17,7 +16,6 @@ The following sample generates C2466:
 ```cpp
 // C2466.cpp
 // compile with: /c
-int i[0];   // C2466
-int j[1];   // OK
-char *p;
+int arr1[0];   // C2466
+int arr2[1];   // OK
 ```

docs/error-messages/compiler-errors-1/compiler-errors-c2200-through-c2299.md

@@ -1,6 +1,6 @@
 ---
-description: "Learn more about: Compiler errors C2200 through C2299"
 title: "Compiler errors C2200 through C2299"
+description: "Learn more about: Compiler errors C2200 through C2299"
 ms.date: "04/21/2019"
 f1_keywords: ["C2202", "C2209", "C2210", "C2211", "C2214", "C2215", "C2221", "C2225", "C2230", "C2235", "C2237", "C2239", "C2240", "C2257", "C2260", "C2263", "C2265", "C2269", "C2278", "C2281", "C2282", "C2284", "C2288", "C2291", "C2294"]
 helpviewer_keywords: ["C2202", "C2209", "C2210", "C2211", "C2214", "C2215", "C2221", "C2225", "C2230", "C2235", "C2237", "C2239", "C2240", "C2257", "C2260", "C2263", "C2265", "C2269", "C2278", "C2281", "C2282", "C2284", "C2288", "C2291", "C2294"]
@@ -98,7 +98,7 @@ The articles in this section of the documentation explain a subset of the error
 |[Compiler error C2280](compiler-error-c2280.md)|'*class*::*function*': attempting to reference a deleted function|
 |Compiler error C2281|'*class*::*function*': a function can only be deleted on the first declaration|
 |Compiler error C2282|'*function1*' cannot override '*function2*'|
-|[Compiler error C2283](compiler-error-c2283.md)|'*identifer*': pure specifier or abstract override specifier not allowed on unnamed class/struct|
+|[Compiler error C2283](compiler-error-c2283.md)|'*identifier*': pure specifier or abstract override specifier not allowed on unnamed struct|
 |Compiler error C2284|'*function*': illegal argument to intrinsic function, parameter *number*|
 |[Compiler error C2285](compiler-error-c2285.md)|pointers to members representation has already been determined - pragma ignored|
 |[Compiler error C2286](compiler-error-c2286.md)|pointers to members of '*identifier*' representation is already set to *inheritance* - declaration ignored|

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

@@ -1,13 +1,13 @@
 ---
-description: "Learn more about: Compiler Warning (level 2) C4251"
 title: "Compiler Warning (level 2) C4251"
+description: "Learn more about: Compiler Warning (level 2) C4251"
 ms.date: 12/01/2023
 f1_keywords: ["C4251"]
 helpviewer_keywords: ["C4251"]
 ---
 # Compiler Warning (level 2) C4251
 
-> '*type*' : class '*type1*' needs to have dll-interface to be used by clients of class '*type2*'
+> '*type*': '*type1*' needs to have dll-interface to be used by clients of '*type2*'
 
 ## Remarks
 

docs/error-messages/compiler-warnings/compiler-warning-level-2-c4099.md

@@ -1,14 +1,13 @@
 ---
-description: "Learn more about: Compiler Warning (level 2) C4099"
 title: "Compiler Warning (level 2) C4099"
+description: "Learn more about: Compiler Warning (level 2) C4099"
 ms.date: "11/04/2016"
 f1_keywords: ["C4099"]
 helpviewer_keywords: ["C4099"]
-ms.assetid: 00bb803d-cae7-4ab8-8969-b46f54139ac8
 ---
 # Compiler Warning (level 2) C4099
 
-'identifier' : type name first seen using 'objecttype1' now seen using 'objecttype2'
+> '*identifier*': type name first seen using '*object_type1*' now seen using '*object_type2*'
 
 An object declared as a structure is defined as a class, or an object declared as a class is defined as a structure. The compiler uses the type given in the definition.
 
@@ -20,5 +19,5 @@ The following sample generates C4099.
 // C4099.cpp
 // compile with: /W2 /c
 struct A;
-class A {};   // C4099, use different identifer or use same object type
+class A {};   // C4099, use different identifier or use same object type
 ```

docs/error-messages/compiler-warnings/compiler-warnings-c4000-through-c4199.md

@@ -1,6 +1,6 @@
 ---
-description: "Table of Microsoft C/C++ compiler (MSVC) warning messages C4000 through C4199"
 title: "Microsoft C/C++ compiler (MSVC) warnings C4000 through C4199"
+description: "Table of Microsoft C/C++ compiler (MSVC) warning messages C4000 through C4199"
 ms.date: "04/21/2019"
 f1_keywords: ["C4023", "C4035", "C4051", "C4060", "C4063", "C4064", "C4065", "C4069", "C4123", "C4137", "C4181", "C4188", "C4193", "C4194", "C4195", "C4196", "C4199"]
 helpviewer_keywords: ["C4023", "C4035", "C4051", "C4060", "C4063", "C4064", "C4065", "C4069", "C4123", "C4137", "C4181", "C4188", "C4193", "C4194", "C4195", "C4196", "C4199"]

docs/error-messages/compiler-warnings/compiler-warnings-c4200-through-c4399.md

@@ -55,7 +55,7 @@ The articles in this section describe Microsoft C/C++ compiler warning messages
 |[Compiler warning (level 2 and level 3 and level 4) C4244](compiler-warning-levels-3-and-4-c4244.md)|'*conversion_type*': conversion from '*type1*' to '*type2*', possible loss of data|
 |[Compiler warning (level 4) C4245](compiler-warning-level-4-c4245.md)|'*conversion_type*': conversion from '*type1*' to '*type2*', signed/unsigned mismatch|
 |[Compiler warning (level 2) C4250](compiler-warning-level-2-c4250.md)|'*classname*': inherits '*base_classname*::*member*' via dominance|
-|[Compiler warning (level 2) C4251](compiler-warning-level-1-c4251.md)|'*object_type1*': '*identifier1*' needs to have dll-interface to be used by clients of '*identfier2*'|
+|[Compiler warning (level 2) C4251](compiler-warning-level-1-c4251.md)|'*type*': '*type1*' needs to have dll-interface to be used by clients of '*type2*'|
 |[Compiler warning (level 4, off) C4254](compiler-warning-level-4-c4254.md)|'*operator*': conversion from '*type1*':'*field_bits*' to '*type2*':'*field_bits*', possible loss of data|
 |[Compiler warning (level 4, off) C4255](compiler-warning-level-4-c4255.md)|'*function*': no function prototype given: converting '()' to '(void)'|
 |[Compiler warning (level 4) C4256](compiler-warning-level-4-c4256.md)|'*function*': constructor for class with virtual bases has '`...`'; calls may not be compatible with older versions of Visual C++|

docs/overview/cpp-conformance-improvements.md

@@ -300,7 +300,7 @@ To fix this warning, either use an equality operator, `value == 9`, if this is w
 
 Visual Studio 2022 version 17.9 contains the following conformance improvements, bug fixes, and behavior changes in the Microsoft C/C++ compiler.
 
-For a broader summary of changes made to the Standard Template Library, see [STL Changelog VS 2022 17.9](https://github.com/microsoft/STL/wiki/Changelog#vs-2022-179).
+For a broader summary of changes made to the Standard Template Library, see [STL Changelog VS 2022 17.9](https://github.com/microsoft/STL/wiki/VS-2022-Changelog#vs-2022-179).
 
 ### Application of `_Alignas` on a structured type in C
 
@@ -389,7 +389,7 @@ The C compiler used to accept the `/FU` option, even though it hasn't support ma
 
 The C++23 named modules `std` and `std.compat` are now available when compiling with `/std:c++20`.
 
-For a broader summary of changes made to the C++ Standard Library, see [STL Changelog VS 2022 17.8](https://github.com/microsoft/STL/wiki/Changelog#vs-2022-178).
+For a broader summary of changes made to the C++ Standard Library, see [STL Changelog VS 2022 17.8](https://github.com/microsoft/STL/wiki/VS-2022-Changelog#vs-2022-178).
 
 ## <a name="improvements_177"></a> Conformance improvements in Visual Studio 2022 version 17.7
 
@@ -405,7 +405,7 @@ The `<print>` library is now supported. See [P2093R14 Formatted output](https://
 
 Implemented `views::cartesian_product`.
 
-For a broader summary of changes made to the Standard Template Library, see [STL Changelog VS 2022 17.7](https://github.com/microsoft/STL/wiki/Changelog#vs-2022-177).
+For a broader summary of changes made to the Standard Template Library, see [STL Changelog VS 2022 17.7](https://github.com/microsoft/STL/wiki/VS-2022-Changelog#vs-2022-177).
 
 ### `using` conformance
 

docs/overview/what-s-new-for-visual-cpp-in-visual-studio.md

@@ -261,7 +261,7 @@ A partial list of new features:
 | For more information about | See |
 |---|---|
 | What's new for C++ developers | [What's new for C++ Developers in Visual Studio 2022 17.9](https://devblogs.microsoft.com/cppblog/whats-new-for-cpp-developers-in-visual-studio-2022-17-9/) |
-| Standard Library (STL) merged C++23 features, performance improvements, enhanced behavior, LWG issue resolutions, and fixed bugs | [STL Changelog 17.9](https://github.com/microsoft/STL/wiki/Changelog#vs-2022-179) |
+| Standard Library (STL) merged C++23 features, performance improvements, enhanced behavior, LWG issue resolutions, and fixed bugs | [STL Changelog 17.9](https://github.com/microsoft/STL/wiki/VS-2022-Changelog#vs-2022-179) |
 | New features in the Visual Studio 17.9 IDE |[Visual Studio 2022 version 17.9 Release Notes](/visualstudio/releases/2022/release-notes-v17.9) |
 | C++ language conformance improvements in Visual Studio 2022 17.9 | [C++ Conformance improvements, behavior changes, and bug fixes in Visual Studio 2022](cpp-conformance-improvements.md#improvements_179) |
 | Summary of C++ backend updates | [MSVC Backend updates since Visual Studio 2022 version 17.3](https://devblogs.microsoft.com/cppblog/msvc-backend-updates-since-visual-studio-2022-version-17-3/) |
@@ -294,7 +294,7 @@ A partial list of new features:
 | For more information about | See |
 |---|---|
 | What's new for C++ developers | [What's new for C++ Developers in Visual Studio 2022 17.8](https://devblogs.microsoft.com/cppblog/whats-new-for-cpp-developers-in-visual-studio-2022-17-8/) |
-| Standard Library (STL) merged C++26, C++23 features, C++20 extensions, LWG issue resolutions, performance improvements, enhanced behavior, and fixed bugs | [STL Changelog 17.8](https://github.com/microsoft/STL/wiki/Changelog#vs-2022-178) |
+| Standard Library (STL) merged C++26, C++23 features, C++20 extensions, LWG issue resolutions, performance improvements, enhanced behavior, and fixed bugs | [STL Changelog 17.8](https://github.com/microsoft/STL/wiki/VS-2022-Changelog#vs-2022-178) |
 | New features in the Visual Studio 17.8 IDE |[Visual Studio 2022 version 17.8 Release Notes](/visualstudio/releases/2022/release-notes-v17.8) |
 | C++ language conformance improvements in Visual Studio 2022 17.8 | [C++ Conformance improvements, behavior changes, and bug fixes in Visual Studio 2022](cpp-conformance-improvements.md#improvements_178) |
 | An overview of C++ improvements in Visual Studio, VS Code, and vcpkg during 2023 | [A year of C++ improvements](https://devblogs.microsoft.com/cppblog/a-year-of-cpp-improvements-in-visual-studio-vs-code-and-vcpkg) |
@@ -554,7 +554,7 @@ In Visual Studio 2022, when you start your app in the debugger, you can use the
 
 ### Standard Library improvements
 
-Select Standard Library (STL) improvements are highlighted here. For a comprehensive list of new functionality, changes, bug fixes, and performance improvements, see the STL team's [Changelog](https://github.com/microsoft/STL/wiki/Changelog#vs-2022).
+Select Standard Library (STL) improvements are highlighted here. For a comprehensive list of new functionality, changes, bug fixes, and performance improvements, see the STL team's [Changelog](https://github.com/microsoft/STL/wiki/Changelog).
 
 - Added debugging visualizers to improve how the following types are displayed: `source_location`, `bind_front()`, `u8string` (and its iterators), `default_sentinel_t`, `unreachable_sentinel_t`, `ranges::empty_view`, `ranges::single_view`, `ranges::iota_view` (and its iterator/sentinel), `ranges::ref_view`, `thread`, `thread::id`, `jthread`, and `filesystem::path`
 - Added `[[nodiscard]]` to the `stoi()` family of functions in `<string>` and to various functions in `<locale>` such as the `collate` member functions, `has_facet()`, and the `isalnum()` and `tolower()` families.