OpenE2K/gcc
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

interface.texi, [...]: Don't mention deprecated target macros.

Browse Source 
* doc/interface.texi, doc/tm.texi, doc/trouble.texi: Don't
	mention deprecated target macros.

From-SVN: r77217
This commit is contained in:
Kazu Hirata 2004-02-04 05:33:13 +00:00 committed by Kazu Hirata
parent a4a4b1d364
commit cea2860314
4 changed files with 11 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gcc/ChangeLog
View File

@ -1,3 +1,8 @@
2004-02-04 Kazu Hirata <kazu@cs.umass.edu>
* doc/interface.texi, doc/tm.texi, doc/trouble.texi: Don't
mention deprecated target macros.
2004-02-04 Kazu Hirata <kazu@cs.umass.edu>
* config.gcc: Remove obsolete ports and configurations.

4
gcc/doc/interface.texi
View File

@ -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

4
gcc/doc/tm.texi
View File

@ -3873,7 +3873,7 @@ known.
@code{FUNCTION_VALUE} is not used for return vales with aggregate data
types, because these are returned in another way. See
@code{STRUCT_VALUE_REGNUM} and related macros, below.
@code{TARGET_STRUCT_VALUE_RTX} and related macros, below.
@end defmac
@defmac FUNCTION_OUTGOING_VALUE (@var{valtype}, @var{func})
@ -3891,7 +3891,7 @@ If @code{FUNCTION_OUTGOING_VALUE} is not defined,
@code{FUNCTION_OUTGOING_VALUE} is not used for return vales with
aggregate data types, because these are returned in another way. See
@code{STRUCT_VALUE_REGNUM} and related macros, below.
@code{TARGET_STRUCT_VALUE_RTX} and related macros, below.
@end defmac
@defmac LIBCALL_VALUE (@var{mode})

4
gcc/doc/trouble.texi
View File

@ -615,8 +615,8 @@ The method used by GCC is as follows: a structure or union which is
1, 2, 4 or 8 bytes long is returned like a scalar. A structure or union
with any other size is stored into an address supplied by the caller
(usually in a special, fixed register, but on some machines it is passed
on the stack). The machine-description macros @code{STRUCT_VALUE} and
@code{STRUCT_INCOMING_VALUE} tell GCC where to pass this address.
on the stack). 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