tree-ssa.texi (Jumps): RESULT_DECL can also be an operand of a RETURN_EXPR

* doc/tree-ssa.texi (Jumps): RESULT_DECL can also be an operand
        of a RETURN_EXPR

From-SVN: r116940
This commit is contained in:
Aldy Hernandez 2006-09-14 01:17:15 +00:00 committed by Aldy Hernandez
parent 3c3f1a6f39
commit f5efb27f74
2 changed files with 9 additions and 4 deletions

View File

@ -1,3 +1,8 @@
2006-09-13 Aldy Hernandez <aldyh@redhat.com>
* doc/tree-ssa.texi (Jumps): RESULT_DECL can also be an operand
of a RETURN_EXPR
2006-09-13 Andrew Pinski <pinskia@physics.uc.edu> 2006-09-13 Andrew Pinski <pinskia@physics.uc.edu>
PR debug/28980 PR debug/28980

View File

@ -399,10 +399,10 @@ Other jumps are expressed by either @code{GOTO_EXPR} or @code{RETURN_EXPR}.
The operand of a @code{GOTO_EXPR} must be either a label or a variable The operand of a @code{GOTO_EXPR} must be either a label or a variable
containing the address to jump to. containing the address to jump to.
The operand of a @code{RETURN_EXPR} is either @code{NULL_TREE} or a The operand of a @code{RETURN_EXPR} is either @code{NULL_TREE},
@code{MODIFY_EXPR} which sets the return value. It would be nice to @code{RESULT_DECL}, or a @code{MODIFY_EXPR} which sets the return value. It
move the @code{MODIFY_EXPR} into a separate statement, but the special would be nice to move the @code{MODIFY_EXPR} into a separate statement, but the
return semantics in @code{expand_return} make that difficult. It may 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 still happen in the future, perhaps by moving most of that logic into
@code{expand_assignment}. @code{expand_assignment}.