From 09fa572c45232c54bebd4f301df52f0112828ce4 Mon Sep 17 00:00:00 2001 From: aldyh Date: Thu, 14 Sep 2006 01:17:15 +0000 Subject: [PATCH 1/1] * doc/tree-ssa.texi (Jumps): RESULT_DECL can also be an operand of a RETURN_EXPR git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@116940 138bc75d-0d04-0410-961f-82ee72b054a4 --- gcc/ChangeLog | 5 +++++ gcc/doc/tree-ssa.texi | 8 ++++---- 2 files changed, 9 insertions(+), 4 deletions(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index b0b36ce1380..3fe8fe5fea8 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,8 @@ +2006-09-13 Aldy Hernandez + + * doc/tree-ssa.texi (Jumps): RESULT_DECL can also be an operand + of a RETURN_EXPR + 2006-09-13 Andrew Pinski PR debug/28980 diff --git a/gcc/doc/tree-ssa.texi b/gcc/doc/tree-ssa.texi index 016f812fed4..9f6b8998adc 100644 --- a/gcc/doc/tree-ssa.texi +++ b/gcc/doc/tree-ssa.texi @@ -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}. -- 2.11.0