《chapt_12 High-Level Language Interface》.ppt

Assembly Language for Intel-Based Computers, 5th Edition Chapter 12: High-Level Language Interface Chapter Overview Introduction Inline Assembly Code Linking to C/C++ in Protected Mode Linking to C/C++ in Real-Address Mode Why Link ASM and HLL Programs? Use high-level language for overall project development Relieves programmer from low-level details Use assembly language code Speed up critical sections of code Access nonstandard hardware devices Write platform-specific code Extend the HLLs capabilities General Conventions Considerations when calling assembly language procedures from high-level languages: Both must use the same naming convention (rules regarding the naming of variables and procedures) Both must use the same memory model, with compatible segment names Both must use the same calling convention Calling Convention Identifies specific registers that must be preserved by procedures Determines how arguments are passed to procedures: in registers, on the stack, in shared memory, etc. Determines the order in which arguments are passed by calling programs to procedures Determines whether arguments are passed by value or by reference Determines how the stack pointer is restored after a procedure call Determines how functions return values External Identifiers An external identifier is a name that has been placed in a module’s object file in such a way that the linker can make the name available to other program modules. The linker resolves references to external identifiers, but can only do so if the same naming convention is used in all program modules. Whats Next Introduction Inline Assembly Code Linking to C/C++ in Protected Mode Linking to C/C++ in Real-Address Mode Inline Assembly Code Assembly language source code that is inserted directly into a HLL program. Compilers such as Microsoft Visual C++ and Borland C++ have compiler-specific directives that identify inline ASM code. Efficient inline code executes quickly because CALL and RET instructions are