This is the mail archive of the gcc@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: Re: LOOP_HEADER tree code?

From: "Devang Patel" <devang dot patel at gmail dot com>
To: "Zdenek Dvorak" <rakdver at atrey dot karlin dot mff dot cuni dot cz>
Cc: gcc at gcc dot gnu dot org
Date: Wed, 25 Oct 2006 13:01:12 -0700
Subject: Re: Re: LOOP_HEADER tree code?
References: <352a1fb20610251031l6294a090sceafabe83e1b98ef@mail.gmail.com> <20061025192037.GA15982@atrey.karlin.mff.cuni.cz>

> However, various optimizer needs to know about this special tree node.
not really (not any more than they know about other tree codes that are
not interesting for them).


If we take an example of Jump Threading pass then it needs to  know
about this tree node and update it properly.

So, the passes that maniuplate loop structure need to know about
LOOP_HEADER and others do not need to worry about LOOP_HEADER.

Now, focusing on the passes that manipulate loop structure. Are these
pass responsible for fixing loop info or is it responsiblity of cleanup pass ?

-
Devang

Follow-Ups:
- Re: Re: LOOP_HEADER tree code?
  - From: Steven Bosscher
- Re: Re: LOOP_HEADER tree code?
  - From: Jeffrey Law

References:
- Re: LOOP_HEADER tree code?
  - From: Devang Patel
- Re: LOOP_HEADER tree code?
  - From: Zdenek Dvorak

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