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

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
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gcc/ChangeLog
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>
PR debug/28980

8
gcc/doc/tree-ssa.texi
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
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}.