This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[patch] fr30.h: Remove a target-independent comment.
- From: Kazu Hirata <kazu at cs dot umass dot edu>
- To: gcc-patches at gcc dot gnu dot org
- Date: Wed, 04 Feb 2004 00:53:29 -0500 (EST)
- Subject: [patch] fr30.h: Remove a target-independent comment.
Hi,
Committed as obvious.
Kazu Hirata
2004-02-04 Kazu Hirata <kazu@cs.umass.edu>
* config/fr30/fr30.h (FUNCTION_VALUE): Remove the
target-independent comment.
Index: fr30.h
===================================================================
RCS file: /cvs/gcc/gcc/gcc/config/fr30/fr30.h,v
retrieving revision 1.48
diff -u -r1.48 fr30.h
--- fr30.h 1 Feb 2004 21:21:36 -0000 1.48
+++ fr30.h 4 Feb 2004 05:46:42 -0000
@@ -783,24 +783,6 @@
/*}}}*/
/*{{{ How Scalar Function Values are Returned. */
-/* A C expression to create an RTX representing the place where a function
- returns a value of data type VALTYPE. VALTYPE is a tree node representing a
- data type. Write `TYPE_MODE (VALTYPE)' to get the machine mode used to
- represent that type. On many machines, only the mode is relevant.
- (Actually, on most machines, scalar values are returned in the same place
- regardless of mode).
-
- If `PROMOTE_FUNCTION_RETURN' is defined, you must apply the same promotion
- rules specified in `PROMOTE_MODE' if VALTYPE is a scalar type.
-
- If the precise function being called is known, FUNC is a tree node
- (`FUNCTION_DECL') for it; otherwise, FUNC is a null pointer. This makes it
- possible to use a different value-returning convention for specific
- functions when all their calls are known.
-
- `FUNCTION_VALUE' is not used for return vales with aggregate data types,
- because these are returned in another way. See `STRUCT_VALUE_REGNUM' and
- related macros, below. */
#define FUNCTION_VALUE(VALTYPE, FUNC) \
gen_rtx_REG (TYPE_MODE (VALTYPE), RETURN_VALUE_REGNUM)