diff options
Diffstat (limited to 'contrib/gcc/doc/interface.texi')
| -rw-r--r-- | contrib/gcc/doc/interface.texi | 27 |
1 files changed, 5 insertions, 22 deletions
diff --git a/contrib/gcc/doc/interface.texi b/contrib/gcc/doc/interface.texi index c554434..b55293d 100644 --- a/contrib/gcc/doc/interface.texi +++ b/contrib/gcc/doc/interface.texi @@ -1,5 +1,5 @@ @c Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, -@c 1999, 2000, 2001 Free Software Foundation, Inc. +@c 1999, 2000, 2001, 2002, 2003, 2004 Free Software Foundation, Inc. @c This is part of the GCC manual. @c For copying conditions, see the file gcc.texi. @@ -28,8 +28,8 @@ long in the same registers used for @code{int} or @code{double} return values. (GCC typically allocates variables of such types in registers also.) Structures and unions of other sizes are returned by storing them into an address passed by the caller (usually in a -register). The machine-description macros @code{STRUCT_VALUE} and -@code{STRUCT_INCOMING_VALUE} tell GCC where to pass this address. +register). The target hook @code{TARGET_STRUCT_VALUE_RTX} +tells GCC where to pass this address. By contrast, PCC on most target machines returns structures and unions of any size by copying the data into an area of static storage, and then @@ -76,27 +76,10 @@ just take the address of the variable. If a variable's address is ever taken, even if just to compute it and ignore it, then the variable cannot go in a register: -@example +@smallexample @{ int careful; &careful; @dots{} @} -@end example - -@cindex arithmetic libraries -@cindex math libraries -@opindex msoft-float -Code compiled with GCC may call certain library routines. Most of -them handle arithmetic for which there are no instructions. This -includes multiply and divide on some machines, and floating point -operations on any machine for which floating point support is disabled -with @option{-msoft-float}. Some standard parts of the C library, such as -@code{bcopy} or @code{memcpy}, are also called automatically. The usual -function call interface is used for calling the library routines. - -Some of these routines can be defined in mostly machine-independent C; -they appear in @file{libgcc2.c}. Others must be hand-written in -assembly language for each processor. Wherever they are defined, they -are compiled into the support library, @file{libgcc.a}, which is -automatically searched when you link programs with GCC@. +@end smallexample |
