Mixed-language programming allows you to combine the unique strengths of Visual C++ with your assembly-language routines. There are some cases where you want to achieve things using inline assembly, such as improving speed, reducing memory needs and getting more efficiency. However, inline assembler is not as powerful as MASM, it does not support macros or directives. This article explains how to write assembly routines that can be called from Visual C++ modules. But before proceeding, there are two terms you have to be familiar with:
It specifies how the compiler alters the symbol name as it places the name in a .OBJ file. For example, a C function “
void func(void)” is put as “_func@0” in the .OBJ file, whereas in C++, it is decorated to “?func@@YAXXZ” in the .OBJ file.
It determines how a language implements a call to a procedure and how the procedure returns to the caller. In the C Calling Convention (
__cdecl), arguments are pushed onto the stack from right to left, the called procedure returns without removing the arguments from the stack. It is the caller’s responsibility to clean the stack after the call.
In Standard Calling Convention (
__stdcall), arguments are pushed onto the stack from right to left, the called procedure cleans the stack if it does not accept a variable number of arguments. In Fast Calling Convention (
__fastcall), the first two parameters are loaded into
edx registers, respectively. The other parameters are pushed onto the stack from right to left. The same function is responsible for cleaning the stack.
Here is a summary table for some calling and naming conventions with an example:
|Language, Calling Convention||Name in .OBJ file||void func (void)|
How to use MASM routines in Visual C++ modules:
The following assembly function (
Addup) accepts three
DWORD (32-bit) values as parameters, and then returns the sum of them. Whenever you write a routine make sure you don't choose it as entry point (i.e. END Addup).
.model flat, stdcall
option casemap :none
Addup PROC, Arg1:DWORD, Arg2:DWORD, Arg3:DWORD
mov eax, Arg1
add eax, Arg2
add eax, Arg3
- Now copy the resultant .obj file (Addup.obj) into your VC++ application’s project folder.
- Add to the C++ source file (.cpp) that will use this routine, the following prototype:
extern “C” int __stdcall Addup (int, int, int);
Or you can put this prototype into a new header file and then add it to your project. The
extern “C” indicates C naming convention since you are in a C++ environment. MASM uses C naming convention when you specify
STDCALL. Finally, the
__stdcall indicates that the routine uses standard calling convention.
- Now add the .OBJ file name (Addup.obj) into your linker commands window. Or you can add the file manually to your project. Otherwise, you will get an “unresolved external” error.
- Now you should compile the project fine without any errors.