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: [PATCH] PR30391: GIMPLE_MODIFY_STMT vs. middle-end

From: Aldy Hernandez <aldyh at redhat dot com>
To: Steven Bosscher <stevenb dot gcc at gmail dot com>
Cc: gcc-patches at gcc dot gnu dot org, Roger Sayle <roger at eyesopen dot com>
Date: Mon, 12 Feb 2007 14:50:42 -0400
Subject: Re: [PATCH] PR30391: GIMPLE_MODIFY_STMT vs. middle-end
References: <9748.68.35.10.103.1170648498.squirrel@mail.eyesopen.com> <200702052037.10964.steven@gcc.gnu.org>

On Mon, Feb 05, 2007 at 08:37:10PM +0100, Steven Bosscher wrote:
> On Monday 05 February 2007 05:08, Roger Sayle wrote:
> >  For example, during RTL expansion we may need to
> > temporarily create assignments to be expanded, and there's no strong
> > reason for these to use the same doubly linked data structure that we use
> > for representing functions.
> 
> Well, one could argue that expand should *only* see GIPMLE, so that
> the expand_* routines can be simplified.  So maybe we should see no
> MODIFY_EXPRs during RTL expandsion, but only GIMPLE_MODIFY_STMTs...

Correct, that was the original intent.

References:
- [PATCH] PR30391: GIMPLE_MODIFY_STMT vs. middle-end
  - From: Roger Sayle
- Re: [PATCH] PR30391: GIMPLE_MODIFY_STMT vs. middle-end
  - From: Steven Bosscher

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