You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/assembler/arm/arm-assembler-diagnostic-messages.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ The Microsoft ARM assembler (*armasm*) emits diagnostic warnings and errors when
17
17
18
18
> A2193: this instruction generates unpredictable behavior
19
19
20
-
The ARM architecture cannot guarantee what happens when this instruction is executed. For details about the well-defined forms of this instruction, consult the [ARM Architecture Reference Manual](http://go.microsoft.com/fwlink/p/?linkid=246464).
20
+
The ARM architecture cannot guarantee what happens when this instruction is executed. For details about the well-defined forms of this instruction, consult the [ARM Architecture Reference Manual](https://go.microsoft.com/fwlink/p/?linkid=246464).
21
21
22
22
```asm
23
23
ADD r0, r8, pc ; A2193: this instruction generates unpredictable behavior
@@ -93,7 +93,7 @@ In ARM mode, there is an alternate syntax for specifying constants. Instead of
93
93
94
94
> A4509: This form of conditional instruction is deprecated
95
95
96
-
This form of conditional instruction has been deprecated by ARM in the ARMv8 architecture. We recommend that you change the code to use conditional branches. To see which conditional instructions are still supported, consult the [ARM Architecture Reference Manual](http://go.microsoft.com/fwlink/p/?linkid=246464).
96
+
This form of conditional instruction has been deprecated by ARM in the ARMv8 architecture. We recommend that you change the code to use conditional branches. To see which conditional instructions are still supported, consult the [ARM Architecture Reference Manual](https://go.microsoft.com/fwlink/p/?linkid=246464).
97
97
98
98
This warning is not emitted when the **-oldit** command-line switch is used.
The system time to be obtained as an HTTP format string.
274
274
275
275
*strTime*<br/>
276
-
A reference to a string variable to receive the HTTP date time as defined in RFC 2616 ([http://www.ietf.org/rfc/rfc2616.txt](http://www.ietf.org/rfc/rfc2616.txt)) and RFC 1123 ([http://www.ietf.org/rfc/rfc1123.txt](http://www.ietf.org/rfc/rfc1123.txt)).
276
+
A reference to a string variable to receive the HTTP date time as defined in RFC 2616 ([https://www.ietf.org/rfc/rfc2616.txt](https://www.ietf.org/rfc/rfc2616.txt)) and RFC 1123 ([https://www.ietf.org/rfc/rfc1123.txt](https://www.ietf.org/rfc/rfc1123.txt)).
Copy file name to clipboardExpand all lines: docs/build/arm-exception-handling.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ The ARM EABI (embedded application binary interface) specifies an exception unwi
15
15
16
16
### Assumptions
17
17
18
-
Executable images for Windows on ARM use the Portable Executable (PE) format. For more information, see [Microsoft PE and COFF Specification](http://go.microsoft.com/fwlink/p/?linkid=84140). Exception handling information is stored in the .pdata and .xdata sections of the image.
18
+
Executable images for Windows on ARM use the Portable Executable (PE) format. For more information, see [Microsoft PE and COFF Specification](https://go.microsoft.com/fwlink/p/?linkid=84140). Exception handling information is stored in the .pdata and .xdata sections of the image.
19
19
20
20
The exception handling mechanism makes certain assumptions about code that follows the ABI for Windows on ARM:
Copy file name to clipboardExpand all lines: docs/build/configuring-programs-for-windows-xp.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,4 +63,4 @@ Due to differences in platform and library support, the development experience f
63
63
64
64
-**Building HLSL**
65
65
66
-
By default, the Windows XP toolset does not compile HLSL source code files. To compile HLSL files, download and install the June 2010 DirectX SDK, and then set the project's VC directories to include it. For more information, see the "DirectX SDK Does Not Register Include/Library Paths with Visual Studio 2010" section of the [June 2010 DirectX SDK download page](http://www.microsoft.com/download/details.aspx?displaylang=en&id=6812).
66
+
By default, the Windows XP toolset does not compile HLSL source code files. To compile HLSL files, download and install the June 2010 DirectX SDK, and then set the project's VC directories to include it. For more information, see the "DirectX SDK Does Not Register Include/Library Paths with Visual Studio 2010" section of the [June 2010 DirectX SDK download page](https://www.microsoft.com/download/details.aspx?displaylang=en&id=6812).
Copy file name to clipboardExpand all lines: docs/build/how-to-modify-the-target-framework-and-platform-toolset.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ You can change Visual Studio C++ project settings to target different versions o
15
15
When you change the target Framework, also change the platform toolset to a version that supports that Framework. For example, to target the .NET Framework 4.5, you must use a compatible platform toolset such as Visual Studio 2015 (v140), Visual Studio 2013 (v120) or Visual Studio 2012 (v110). You can use the **Windows7.1SDK** platform toolset to target the .NET Framework 2.0, 3.0, 3.5, and 4, and the x86, Itanium, and x64 platforms.
16
16
17
17
> [!NOTE]
18
-
> To change the target platform toolset, you must have the associated version of Visual Studio or the Windows Platform SDK installed. For example, to target the Itanium platform with the **Windows7.1SDK** platform toolset, you must have [Microsoft Windows SDK for Windows 7 and .NET Framework 4 SP1](http://www.microsoft.com/download/details.aspx?id=8279) installed; however, you could use another compatible version of Visual Studio to do your development work, provided that you target the correct Framework version and platform toolset.
18
+
> To change the target platform toolset, you must have the associated version of Visual Studio or the Windows Platform SDK installed. For example, to target the Itanium platform with the **Windows7.1SDK** platform toolset, you must have [Microsoft Windows SDK for Windows 7 and .NET Framework 4 SP1](https://www.microsoft.com/download/details.aspx?id=8279) installed; however, you could use another compatible version of Visual Studio to do your development work, provided that you target the correct Framework version and platform toolset.
19
19
20
20
You can extend the target platform further by creating a custom platform toolset. For more information, see [C++ Native Multi-Targeting](https://blogs.msdn.microsoft.com/vcblog/2009/12/08/c-native-multi-targeting/) on the Visual C++ blog.
Copy file name to clipboardExpand all lines: docs/build/reference/dot-obj-files-as-linker-input.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,13 +15,13 @@ Microsoft provides a complete description of the common object file format. For
15
15
16
16
Starting with Visual Studio 2005, the Microsoft MSVC compiler supports Unicode characters in identifiers as defined by the ISO/IEC C and C++ standards. Previous versions of the compiler supported only ASCII characters in identifiers. To support Unicode in the names of functions, classes, and statics, the compiler and linker use the Unicode UTF-8 encoding for COFF symbols in .obj files. The UTF-8 encoding is upwardly compatible with the ASCII encoding used by earlier versions of Visual Studio.
17
17
18
-
For more information about the compiler and linker, see [Unicode Support in the Compiler and Linker](unicode-support-in-the-compiler-and-linker.md). For more information about the Unicode standard, see the [Unicode](http://www.unicode.org/) organization.
18
+
For more information about the compiler and linker, see [Unicode Support in the Compiler and Linker](unicode-support-in-the-compiler-and-linker.md). For more information about the Unicode standard, see the [Unicode](https://www.unicode.org/) organization.
19
19
20
20
## See also
21
21
22
22
[LINK Input Files](link-input-files.md)<br/>
23
23
[MSVC Linker Options](linker-options.md)<br/>
24
24
[Support for Unicode](../../text/support-for-unicode.md)<br/>
25
25
[Unicode Support in the Compiler and Linker](unicode-support-in-the-compiler-and-linker.md)<br/>
Copy file name to clipboardExpand all lines: docs/build/reference/gd-gr-gv-gz-calling-convention.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ These options determine the order in which function arguments are pushed onto th
24
24
25
25
**/Gz** specifies the `__stdcall` calling convention for all functions except C++ member functions, functions named `main`, and functions that are marked `__cdecl`, `__fastcall`, or `__vectorcall`. All `__stdcall` functions must have prototypes. This calling convention is only available in compilers that target x86, and is ignored by compilers that target other architectures.
26
26
27
-
**/Gv** specifies the `__vectorcall` calling convention for all functions except C++ member functions, functions named main, functions with a `vararg` variable argument list, or functions that are marked with a conflicting `__cdecl`, `__stdcall`, or `__fastcall` attribute. This calling convention is only available on x86 and x64 architectures that support /arch:SSE2 and above, and is ignored by compilers that target the ARM architecture.
27
+
**/Gv** specifies the `__vectorcall` calling convention for all functions except C++ member functions, functions named `main`, functions with a `vararg` variable argument list, or functions that are marked with a conflicting `__cdecl`, `__stdcall`, or `__fastcall` attribute. This calling convention is only available on x86 and x64 architectures that support /arch:SSE2 and above, and is ignored by compilers that target the ARM architecture.
28
28
29
29
Functions that take a variable number of arguments must be marked `__cdecl`.
Copy file name to clipboardExpand all lines: docs/build/reference/gf-eliminate-duplicate-strings.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ char *t = "This is a character buffer";
34
34
> [!NOTE]
35
35
> The **/GF** compiler option creates an addressable section for each unique string. And by default, an object file can contain up to 65,536 addressable sections. If your program contains more than 65,536 strings, use the [/bigobj](bigobj-increase-number-of-sections-in-dot-obj-file.md) compiler option to create more sections.
36
36
37
-
**/GF** is in effect when [/O1](o1-o2-minimize-size-maximize-speed.md) or **/O2** is used.
37
+
**/GF** is in effect when [/O1](o1-o2-minimize-size-maximize-speed.md) or [/O2](o1-o2-minimize-size-maximize-speed.md) is used.
38
38
39
39
### To set this compiler option in the Visual Studio development environment
0 commit comments