forked from Imagelibrary/rtems
133 lines
4.9 KiB
Perl
133 lines
4.9 KiB
Perl
@c
|
|
@c COPYRIGHT (c) 1988-1998.
|
|
@c On-Line Applications Research Corporation (OAR).
|
|
@c All rights reserved.
|
|
@c
|
|
@c $Id$
|
|
@c
|
|
|
|
@ifinfo
|
|
@node Calling Conventions, Calling Conventions Introduction, CPU Model Dependent Features Floating Point Unit, Top
|
|
@end ifinfo
|
|
@chapter Calling Conventions
|
|
@ifinfo
|
|
@menu
|
|
* Calling Conventions Introduction::
|
|
* Calling Conventions Processor Background::
|
|
* Calling Conventions Calling Mechanism::
|
|
* Calling Conventions Register Usage::
|
|
* Calling Conventions Parameter Passing::
|
|
* Calling Conventions User-Provided Routines::
|
|
* Calling Conventions Leaf Procedures::
|
|
@end menu
|
|
@end ifinfo
|
|
|
|
@ifinfo
|
|
@node Calling Conventions Introduction, Calling Conventions Processor Background, Calling Conventions, Calling Conventions
|
|
@end ifinfo
|
|
@section Introduction
|
|
|
|
Each high-level language compiler generates
|
|
subroutine entry and exit code based upon a set of rules known
|
|
as the compiler's calling convention. These rules address the
|
|
following issues:
|
|
|
|
@itemize @bullet
|
|
@item register preservation and usage
|
|
|
|
@item parameter passing
|
|
|
|
@item call and return mechanism
|
|
@end itemize
|
|
|
|
A compiler's calling convention is of importance when
|
|
interfacing to subroutines written in another language either
|
|
assembly or high-level. Even when the high-level language and
|
|
target processor are the same, different compilers may use
|
|
different calling conventions. As a result, calling conventions
|
|
are both processor and compiler dependent.
|
|
|
|
@ifinfo
|
|
@node Calling Conventions Processor Background, Calling Conventions Calling Mechanism, Calling Conventions Introduction, Calling Conventions
|
|
@end ifinfo
|
|
@section Processor Background
|
|
|
|
All members of the i960 architecture family support
|
|
two methods for performing procedure calls: a RISC-style
|
|
branch-and-link and an integrated call and return mechanism.
|
|
|
|
On a branch-and-link, the processor branches to the
|
|
invoked procedure and saves the return address in a register,
|
|
G14. Typically, the invoked procedure will not invoke another
|
|
procedure and is referred to as a leaf procedure. Many
|
|
high-level language compilers for the i960 family recognize leaf
|
|
procedures and automatically optimize them to utilize the
|
|
branch-and-link mechanism. Branch-and-link procedures are
|
|
invoked using the bal and balx instructions and return control
|
|
via the bx instruction. By convention, G14 is zero when not in
|
|
a leaf procedure. It is the responsibility of the leaf
|
|
procedure to clear G14 before returning.
|
|
|
|
The integrated call and return mechanism also
|
|
branches to the invoked procedure and saves the return address
|
|
as did the branch and link mechanism. However, the important
|
|
difference is that the call, callx, and calls instructions save
|
|
the local register set (R0 through R15) before transferring
|
|
control to the invoked procedure. The ret instruction
|
|
automatically restores the previous local register set. The
|
|
i960CA provides a register cache which can be configured to
|
|
retain the last five to sixteen recent register caches. When
|
|
the register cache is full, the oldest cached register set is
|
|
written to the stack.
|
|
|
|
@ifinfo
|
|
@node Calling Conventions Calling Mechanism, Calling Conventions Register Usage, Calling Conventions Processor Background, Calling Conventions
|
|
@end ifinfo
|
|
@section Calling Mechanism
|
|
|
|
All RTEMS directives are invoked using either a call
|
|
or callx instruction and return to the user via the ret
|
|
instruction.
|
|
|
|
@ifinfo
|
|
@node Calling Conventions Register Usage, Calling Conventions Parameter Passing, Calling Conventions Calling Mechanism, Calling Conventions
|
|
@end ifinfo
|
|
@section Register Usage
|
|
|
|
As discussed above, the call and callx instructions
|
|
automatically save the current contents of the local register
|
|
set (R0 through R15). The contents of the local registers will
|
|
be restored as part of returning to the application. The
|
|
contents of global registers G0 through G7 are not preserved by
|
|
RTEMS directives.
|
|
|
|
@ifinfo
|
|
@node Calling Conventions Parameter Passing, Calling Conventions User-Provided Routines, Calling Conventions Register Usage, Calling Conventions
|
|
@end ifinfo
|
|
@section Parameter Passing
|
|
|
|
RTEMS uses the standard i960 family C parameter
|
|
passing mechanism in which G0 contains the first parameter, G1
|
|
the second, and so on for the remaining parameters. No RTEMS
|
|
directive requires more than six parameters.
|
|
|
|
@ifinfo
|
|
@node Calling Conventions User-Provided Routines, Calling Conventions Leaf Procedures, Calling Conventions Parameter Passing, Calling Conventions
|
|
@end ifinfo
|
|
@section User-Provided Routines
|
|
|
|
All user-provided routines invoked by RTEMS, such as
|
|
user extensions, device drivers, and MPCI routines, must also
|
|
adhere to these calling conventions.
|
|
|
|
@ifinfo
|
|
@node Calling Conventions Leaf Procedures, Memory Model, Calling Conventions User-Provided Routines, Calling Conventions
|
|
@end ifinfo
|
|
@section Leaf Procedures
|
|
|
|
RTEMS utilizes leaf procedures internally to improve
|
|
performance. This improves execution speed as well as reducing
|
|
stack usage and the number of register sets which must be cached.
|
|
|
|
|