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]

Re: [tuples] fix gimplify_return_expr buglet

On 7/20/07, Aldy Hernandez <aldyh@redhat.com> wrote: 
> I think we are still mis-gimplifying this.  The operand we return should
> never be a MODIFY_EXPR.  I don't remember if we've fixed this yet but I
> think not.

What do you mean? 

What about the return tuple to take two operands?  The return decl and
and decl which is setting the return decl?  If the setting decl is
NULL, then we had RETURN_EXRP<RETURN_DECL>; if both are NULL then we
had RETURN_EXPR<>; otherwise we had
RETURN_EXPR<MODIFY_EXPR<RETURN_DECL, OTHER_DECL> >.

Thanks,
Andrew Pinski

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