Skip to content

Commit 06751d7

Browse files
ShannonLeavittShannonLeavitt
authored
Merge pull request MicrosoftDocs#1987 from mikeblome/mb-visualcpp-3
more fixes for Visual C++
2 parents 5cd2657 + 7bf0952 commit 06751d7

126 files changed

Lines changed: 233 additions & 233 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.

‎docs/assembler/inline/asm.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ If used without braces, the `__asm` keyword means that the rest of the line is a
3030

3131
Since the `__asm` keyword is a statement separator, you can put assembly instructions on the same line.
3232

33-
Before Visual C++ 2005, the instruction
33+
Before Visual Studio 2005, the instruction
3434

3535
```cpp
3636
__asm int 3

‎docs/assembler/inline/instruction-set-for-inline-assembly.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.assetid: a45b5b22-9b5f-4545-81ec-70eb8ea2ef9b
99

1010
**Microsoft Specific**
1111

12-
The Visual C++ compiler supports all opcodes through the Pentium 4 and AMD Athlon. Additional instructions supported by the target processor can be created with the [_emit Pseudoinstruction](../../assembler/inline/emit-pseudoinstruction.md).
12+
The Microsoft C++ compiler supports all opcodes through the Pentium 4 and AMD Athlon. Additional instructions supported by the target processor can be created with the [_emit Pseudoinstruction](../../assembler/inline/emit-pseudoinstruction.md).
1313

1414
**END Microsoft Specific**
1515

‎docs/assembler/inline/intel-s-mmx-instruction-set.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.assetid: 705deb2d-c3fd-4696-9e22-8bcf25866daf
99

1010
**Microsoft Specific**
1111

12-
The Visual C++ compiler allows you to use Intel's MMX (multimedia extension) instruction set in the inline assembler. The MMX instructions are also supported by the debugger disassembly. The compiler generates a warning message if the function contains MMX instructions but does not contain an EMMS instruction to empty the multimedia state. For more information, see the Intel Web site.
12+
The Microsoft C++ compiler allows you to use Intel's MMX (multimedia extension) instruction set in the inline assembler. The MMX instructions are also supported by the debugger disassembly. The compiler generates a warning message if the function contains MMX instructions but does not contain an EMMS instruction to empty the multimedia state. For more information, see the Intel Web site.
1313

1414
**END Microsoft Specific**
1515

‎docs/assembler/masm/masm-for-x64-ml64-exe.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,13 +12,13 @@ To use MASM to build code for x64 targets on the command line, you must use a de
1212

1313
For information on ml64.exe command line options, see [ML and ML64 Command-Line Reference](../../assembler/masm/ml-and-ml64-command-line-reference.md).
1414

15-
Inline assembler or use of the ASM keyword is not supported for x64 or ARM targets. To port your x86 code that uses inline assembler to x64 or ARM, you can convert your code to C++, use compiler intrinsics, or create assembler-language source files. The Visual C++ compiler supports intrinsics to allow you to use special-function instructions, for example, privileged, bit scan/test, interlocked, and so on, in as close to a cross-platform manner as possible. For information on available intrinsics, see [Compiler Intrinsics](../../intrinsics/compiler-intrinsics.md).
15+
Inline assembler or use of the ASM keyword is not supported for x64 or ARM targets. To port your x86 code that uses inline assembler to x64 or ARM, you can convert your code to C++, use compiler intrinsics, or create assembler-language source files. The Microsoft C++ compiler supports intrinsics to allow you to use special-function instructions, for example, privileged, bit scan/test, interlocked, and so on, in as close to a cross-platform manner as possible. For information on available intrinsics, see [Compiler Intrinsics](../../intrinsics/compiler-intrinsics.md).
1616

17-
## Add an assembler-language file to a Visual C++ project
17+
## Add an assembler-language file to a Visual Studio C++ project
1818

1919
The Visual Studio project system supports assembler-language files built by using MASM in your C++ projects. You can create x64 assembler-language source files and build them into object files by using MASM, which supports x64 fully. You can then link these object files to your C++ code built for x64 targets. This is one way to overcome the lack of an x64 inline assembler.
2020

21-
### To add an assembler-language file to an existing Visual C++ project
21+
### To add an assembler-language file to an existing Visual Studio C++ project
2222

2323
1. Select the project in **Solution Explorer**. On the menu bar, choose **Project**, **Build Customizations**.
2424

‎docs/atl/reference/creating-an-atl-project.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ The easiest way to create an ATL project is to use the ATL Project Wizard, locat
2222
2323
1. Click **Finish** to close the wizard and open your new project in the development environment.
2424

25-
Once your project is created, you can view the files created in **Solution Explorer**. For more information about the files the wizard creates for your project, see the project-generated file ReadMe.txt. For more information about the file types, see [File Types Created for Visual C++ Projects](../../build/reference/file-types-created-for-visual-cpp-projects.md). For more information about the configurations for the new ATL project, and how to change them, see [Default ATL Project Configurations](../../atl/reference/default-atl-project-configurations.md).
25+
Once your project is created, you can view the files created in **Solution Explorer**. For more information about the files the wizard creates for your project, see the project-generated file ReadMe.txt. For more information about the file types, see [File Types Created for Visual C++ projects](../../build/reference/file-types-created-for-visual-cpp-projects.md). For more information about the configurations for the new ATL project, and how to change them, see [Default ATL Project Configurations](../../atl/reference/default-atl-project-configurations.md).
2626

2727
## See also
2828

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ The Windows XP platform toolset that's included in Visual Studio is a version of
1919

2020
1. In **Solution Explorer**, open the shortcut menu for your project, and then choose **Properties**.
2121

22-
1. In the **Property Pages** dialog box for the project, under **Configuration Properties** > **General**, set the **Platform Toolset** property to the desired Windows XP toolset. For example, choose **Visual Studio 2017 - Windows XP (v141_xp)** to create code for Windows XP and Windows Server 2003 by using the Microsoft Visual C++ 2017 compiler.
22+
1. In the **Property Pages** dialog box for the project, under **Configuration Properties** > **General**, set the **Platform Toolset** property to the desired Windows XP toolset. For example, choose **Visual Studio 2017 - Windows XP (v141_xp)** to create code for Windows XP and Windows Server 2003 by using the Microsoft C++ compiler in Visual Studio 2017.
2323

2424
### C++ runtime support
2525

‎docs/build/creating-and-managing-visual-cpp-projects.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "Visual Studio Projects - C++"
33
ms.date: "12/12/2018"
4-
helpviewer_keywords: ["ATL projects, creating", "Visual C++ projects, creating", "projects [C++], creating", "Visual C++ projects", "ATL projects"]
4+
helpviewer_keywords: ["ATL projects, creating", "Visual Studio C++ projects, creating", "projects [C++], creating", "Visual Studio C++ projects", "ATL projects"]
55
ms.assetid: 11003cd8-9046-4630-a189-a32bf3b88047
66
---
77
# Visual Studio projects - C++

‎docs/build/how-to-configure-visual-cpp-projects-to-target-64-bit-platforms.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
2-
title: "How to: Configure Visual C++ Projects to Target 64-Bit, x64 Platforms"
2+
title: "How to: Configure Visual Studio C++ projects to Target 64-Bit, x64 Platforms"
33
ms.date: "11/04/2016"
44
helpviewer_keywords: ["platforms [C++], 64-bit", "64-bit programming [C++], configuring projects", "project configurations [C++]"]
55
ms.assetid: 2b9ae001-df36-4750-83b2-982145d632ad
66
---
7-
# How to: Configure Visual C++ Projects to Target 64-Bit, x64 Platforms
7+
# How to: Configure Visual Studio C++ projects to Target 64-Bit, x64 Platforms
88

99
You can use the project configurations in the Visual Studio IDE to set up C++ applications to target 64-bit, x64 platforms. You can also migrate Win32 project settings into a 64-bit project configuration.
1010

‎docs/build/reference/atl-program-or-control-source-and-header-files.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,6 @@ All of these files are located in the *Projname* directory, and in either the He
2020

2121
## See also
2222

23-
[File Types Created for Visual C++ Projects](file-types-created-for-visual-cpp-projects.md)<br>
23+
[File Types Created for Visual C++ projects](file-types-created-for-visual-cpp-projects.md)<br>
2424
[MFC Program or Control Source and Header Files](mfc-program-or-control-source-and-header-files.md)<br>
2525
[CLR Projects](files-created-for-clr-projects.md)

‎docs/build/reference/clr-common-language-runtime-compilation.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ One or more of the following switches, comma-separated.
3838

3939
A managed program that does not have assembly metadata in the manifest is known as a *module*. The **noAssembly** option can be used only to produce a module. If you compile by using [/c](c-compile-without-linking.md) and **/clr:noAssembly**, then specify the [/NOASSEMBLY](noassembly-create-a-msil-module.md) option in the linker phase to create a module.
4040

41-
Before Visual C++ 2005, **/clr:noAssembly** required **/LD**. **/LD** is now implied when you specify **/clr:noAssembly**.
41+
Before Visual Studio 2005, **/clr:noAssembly** required **/LD**. **/LD** is now implied when you specify **/clr:noAssembly**.
4242

4343
- **initialAppDomain**
4444

0 commit comments

Comments
 (0)