This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

patch: fix RESULT_DECL gimple docs


There is a discrepancy between the grammar in tree-ssa.texi and the
documentation.

Is this ok?

	* doc/tree-ssa.texi (Jumps): RESULT_DECL can also be an operand
	of a RETURN_EXPR
Index: doc/tree-ssa.texi
===================================================================
--- doc/tree-ssa.texi	(revision 116887)
+++ doc/tree-ssa.texi	(working copy)
@@ -399,10 +399,10 @@ Other jumps are expressed by either @cod
 The operand of a @code{GOTO_EXPR} must be either a label or a variable
 containing the address to jump to.
 
-The operand of a @code{RETURN_EXPR} is either @code{NULL_TREE} or a
-@code{MODIFY_EXPR} which sets the return value.  It would be nice to
-move the @code{MODIFY_EXPR} into a separate statement, but the special
-return semantics in @code{expand_return} make that difficult.  It may
+The operand of a @code{RETURN_EXPR} is either @code{NULL_TREE},
+@code{RESULT_DECL}, or a @code{MODIFY_EXPR} which sets the return value.  It
+would be nice to move the @code{MODIFY_EXPR} into a separate statement, but the
+special return semantics in @code{expand_return} make that difficult.  It may
 still happen in the future, perhaps by moving most of that logic into
 @code{expand_assignment}.
 


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]