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]: Fix places where we expect non-null loops in the looparray

From: Daniel Berlin <dberlin at dberlin dot org>
To: Zdenek Dvorak <rakdver at atrey dot karlin dot mff dot cuni dot cz>
Cc: Dale Johannesen <dalej at apple dot com>, gcc-patches at gcc dot gnu dot org, Andrew MacLeod <amacleod at redhat dot com>, Diego Novillo <dnovillo at redhat dot com>
Date: Tue, 7 Dec 2004 18:05:13 -0500 (EST)
Subject: Re: [PATCH]: Fix places where we expect non-null loops in the looparray
References: <11990EBE-48A2-11D9-A4DB-000A95D7CD40@apple.com><20041207230057.GB20748@atrey.karlin.mff.cuni.cz>

On Wed, 8 Dec 2004, Zdenek Dvorak wrote:

Hello,

easily
get by accident (i.e. a lurking bug).


no, it is expected behavior.  As for why I decided to do it this way --
so that the numbers of the loops do not change in the middle of an
optimization (so you can for example store some information for loops
in an array indexed by loop numbers).  I do not think it is seriously
used anywhere (except perhaps for scev, that store loop numbers in
CHREC nodes).

SCEV also depends on the indexes being in a certain order (DFS order in this case). Is this behavior guaranteed?

Follow-Ups:
- Re: [PATCH]: Fix places where we expect non-null loops in the loop array
  - From: Zdenek Dvorak

References:
- Re: [PATCH]: Fix places where we expect non-null loops in the loop array
  - From: Dale Johannesen
- Re: [PATCH]: Fix places where we expect non-null loops in the loop array
  - From: Zdenek Dvorak

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