Skip to content

Commit d33e3ff

Browse files
author
mikeblome
committed
Merge branch 'master' into mb-linux-asan
merge with master
2 parents bb3704e + 206b58e commit d33e3ff

72 files changed

Lines changed: 1084 additions & 923 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎.openpublishing.redirection.json‎

Lines changed: 310 additions & 20 deletions
Large diffs are not rendered by default.

‎docs/atl/reference/atl-http-utility-functions.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -273,7 +273,7 @@ inline void SystemTimeToHttpDate(
273273
The system time to be obtained as an HTTP format string.
274274

275275
*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)).
277277

278278
## See also
279279

‎docs/atl/reference/atl-text-encoding-functions.md‎

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -267,7 +267,7 @@ Returns TRUE on success, FALSE on failure.
267267

268268
### Remarks
269269

270-
The "B" encoding scheme is described in RFC 2047 ([http://www.ietf.org/rfc/rfc2047.txt](http://www.ietf.org/rfc/rfc2047.txt)).
270+
The "B" encoding scheme is described in RFC 2047 ([https://www.ietf.org/rfc/rfc2047.txt](https://www.ietf.org/rfc/rfc2047.txt)).
271271

272272
## <a name="bencodegetrequiredlength"></a> BEncodeGetRequiredLength
273273

@@ -291,7 +291,7 @@ The number of characters required for a buffer that could hold encoded data of *
291291

292292
### Remarks
293293

294-
The "B" encoding scheme is described in RFC 2047 ([http://www.ietf.org/rfc/rfc2047.txt](http://www.ietf.org/rfc/rfc2047.txt)).
294+
The "B" encoding scheme is described in RFC 2047 ([https://www.ietf.org/rfc/rfc2047.txt](https://www.ietf.org/rfc/rfc2047.txt)).
295295

296296
## <a name="escapexml"></a> EscapeXML
297297

@@ -419,7 +419,7 @@ Returns TRUE on success, FALSE on failure.
419419

420420
### Remarks
421421

422-
The "Q" encoding scheme is described in RFC 2047 ([http://www.ietf.org/rfc/rfc2047.txt](http://www.ietf.org/rfc/rfc2047.txt)).
422+
The "Q" encoding scheme is described in RFC 2047 ([https://www.ietf.org/rfc/rfc2047.txt](https://www.ietf.org/rfc/rfc2047.txt)).
423423

424424
## <a name="qencodegetrequiredlength"></a> QEncodeGetRequiredLength
425425

@@ -443,7 +443,7 @@ The number of characters required for a buffer that could hold encoded data of *
443443

444444
### Remarks
445445

446-
The "Q" encoding scheme is described in RFC 2047 ([http://www.ietf.org/rfc/rfc2047.txt](http://www.ietf.org/rfc/rfc2047.txt)).
446+
The "Q" encoding scheme is described in RFC 2047 ([https://www.ietf.org/rfc/rfc2047.txt](https://www.ietf.org/rfc/rfc2047.txt)).
447447

448448
## <a name="qpdecode"></a> QPDecode
449449

@@ -481,7 +481,7 @@ Returns TRUE on success, FALSE on failure.
481481

482482
### Remarks
483483

484-
The quoted-printable encoding scheme is described in RFC 2045 ([http://www.ietf.org/rfc/rfc2045.txt](http://www.ietf.org/rfc/rfc2045.txt)).
484+
The quoted-printable encoding scheme is described in RFC 2045 ([https://www.ietf.org/rfc/rfc2045.txt](https://www.ietf.org/rfc/rfc2045.txt)).
485485

486486
## <a name="qpdecodegetrequiredlength"></a> QPDecodeGetRequiredLength
487487

@@ -502,7 +502,7 @@ The number of bytes required for a buffer that could hold a decoded string of *n
502502

503503
### Remarks
504504

505-
The quoted-printable encoding scheme is described in RFC 2045 ([http://www.ietf.org/rfc/rfc2045.txt](http://www.ietf.org/rfc/rfc2045.txt)).
505+
The quoted-printable encoding scheme is described in RFC 2045 ([https://www.ietf.org/rfc/rfc2045.txt](https://www.ietf.org/rfc/rfc2045.txt)).
506506

507507
## <a name="qpencode"></a> QPEncode
508508

@@ -538,15 +538,15 @@ ATLSMTP_QPENCODE flags describing how the conversion is to be performed.
538538

539539
- ATLSMTP_QPENCODE_TRAILING_SOFT Appends `=\r\n` to the encoded string.
540540

541-
The quoted-printable encoding scheme is described in [RFC 2045](http://www.ietf.org/rfc/rfc2045.txt).
541+
The quoted-printable encoding scheme is described in [RFC 2045](https://www.ietf.org/rfc/rfc2045.txt).
542542

543543
### Return Value
544544

545545
Returns TRUE on success, FALSE on failure.
546546

547547
### Remarks
548548

549-
The quoted-printable encoding scheme is described in RFC 2045 ([http://www.ietf.org/rfc/rfc2045.txt](http://www.ietf.org/rfc/rfc2045.txt)).
549+
The quoted-printable encoding scheme is described in RFC 2045 ([https://www.ietf.org/rfc/rfc2045.txt](https://www.ietf.org/rfc/rfc2045.txt)).
550550

551551
## <a name="qpencodegetrequiredlength"></a> QPEncodeGetRequiredLength
552552

@@ -567,7 +567,7 @@ The number of characters required for a buffer that could hold encoded data of *
567567

568568
### Remarks
569569

570-
The quoted-printable encoding scheme is described in RFC 2045 ([http://www.ietf.org/rfc/rfc2045.txt](http://www.ietf.org/rfc/rfc2045.txt)).
570+
The quoted-printable encoding scheme is described in RFC 2045 ([https://www.ietf.org/rfc/rfc2045.txt](https://www.ietf.org/rfc/rfc2045.txt)).
571571

572572
## <a name="uudecode"></a> UUDecode
573573

‎docs/build/configuring-programs-for-windows-xp.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -63,4 +63,4 @@ Due to differences in platform and library support, the development experience f
6363

6464
- **Building HLSL**
6565

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).

‎docs/build/how-to-modify-the-target-framework-and-platform-toolset.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ You can change Visual Studio C++ project settings to target different versions o
1515
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.
1616

1717
> [!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.
1919
2020
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.
2121

‎docs/build/reference/dot-obj-files-as-linker-input.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,13 +15,13 @@ Microsoft provides a complete description of the common object file format. For
1515

1616
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.
1717

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.
1919

2020
## See also
2121

2222
[LINK Input Files](link-input-files.md)<br/>
2323
[MSVC Linker Options](linker-options.md)<br/>
2424
[Support for Unicode](../../text/support-for-unicode.md)<br/>
2525
[Unicode Support in the Compiler and Linker](unicode-support-in-the-compiler-and-linker.md)<br/>
26-
[Unicode standard](http://www.unicode.org/)<br/>
26+
[Unicode standard](https://www.unicode.org/)<br/>
2727
[PE Format](/windows/desktop/Debug/pe-format)

‎docs/build/reference/gd-gr-gv-gz-calling-convention.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ These options determine the order in which function arguments are pushed onto th
2424

2525
**/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.
2626

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.
2828

2929
Functions that take a variable number of arguments must be marked `__cdecl`.
3030

‎docs/build/reference/gf-eliminate-duplicate-strings.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ char *t = "This is a character buffer";
3434
> [!NOTE]
3535
> 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.
3636
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.
3838

3939
### To set this compiler option in the Visual Studio development environment
4040

‎docs/build/reference/gw-optimize-global-data.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ When you compile and link separately, you can use the [/OPT:REF](opt-optimizatio
2323

2424
You can also use the [/OPT:ICF](opt-optimizations.md) and [/LTCG](ltcg-link-time-code-generation.md) linker options together to merge in the executable any identical read-only global data across multiple object files compiled with the **/Gw** option.
2525

26-
For more information, see [Introducing /Gw Compiler Switch](http://blogs.msdn.com/b/vcblog/archive/2013/09/11/introducing-gw-compiler-switch.aspx) on the Visual C++ Team Blog.
26+
For more information, see [Introducing /Gw Compiler Switch](https://devblogs.microsoft.com/cppblog/introducing-gw-compiler-switch/) on the C++ Team Blog.
2727

2828
### To set this compiler option in the Visual Studio development environment
2929

‎docs/build/reference/integritycheck-require-signature-check.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ Specifies that the digital signature of the binary image must be checked at load
1515

1616
By default, **/INTEGRITYCHECK** is off.
1717

18-
The **/INTEGRITYCHECK** option sets—in the PE header of the DLL file or executable file—a flag for the memory manager to check for a digital signature in order to load the image in Windows. This option must be set for both 32-bit and 64-bit DLLs that implement kernel-mode code loaded by certain Windows features, and is recommended for all device drivers on Windows Vista, Windows 7, Windows 8, Windows Server 2008, and Windows Server 2012. Versions of Windows prior to Windows Vista ignore this flag. For more information, see [Forced Integrity Signing of Portable Executable (PE) files](http://social.technet.microsoft.com/wiki/contents/articles/255.forced-integrity-signing-of-portable-executable-pe-files.aspx).
18+
The **/INTEGRITYCHECK** option sets—in the PE header of the DLL file or executable file—a flag for the memory manager to check for a digital signature in order to load the image in Windows. This option must be set for both 32-bit and 64-bit DLLs that implement kernel-mode code loaded by certain Windows features, and is recommended for all device drivers on Windows Vista, Windows 7, Windows 8, Windows Server 2008, and Windows Server 2012. Versions of Windows prior to Windows Vista ignore this flag. For more information, see [Forced Integrity Signing of Portable Executable (PE) files](https://social.technet.microsoft.com/wiki/contents/articles/255.forced-integrity-signing-of-portable-executable-pe-files.aspx).
1919

2020
### To set this linker option in Visual Studio
2121

@@ -33,6 +33,6 @@ The **/INTEGRITYCHECK** option sets—in the PE header of the DLL file or execut
3333

3434
[MSVC linker reference](linking.md)<br/>
3535
[MSVC Linker Options](linker-options.md)<br/>
36-
[Forced Integrity Signing of Portable Executable (PE) files](http://social.technet.microsoft.com/wiki/contents/articles/255.forced-integrity-signing-of-portable-executable-pe-files.aspx)<br/>
36+
[Forced Integrity Signing of Portable Executable (PE) files](https://social.technet.microsoft.com/wiki/contents/articles/255.forced-integrity-signing-of-portable-executable-pe-files.aspx)<br/>
3737
[Kernel-Mode Code Signing Walkthrough](https://msdn.microsoft.com/windows/hardware/gg487328.aspx)<br/>
3838
[AppInit DLLs in Windows 7 and Windows Server 2008](https://msdn.microsoft.com/windows/hardware/gg463040.aspx)

0 commit comments

Comments
 (0)