llvm dev - Apr 2010 - [LLVMdev] The "scope" of passes

> Personally, I would make everything a FunctionPass.  
What if a FunctionPass requires the results of a LoopPass? Is there a way to get
all loops of a function without using LoopPass and LoopInfo?

On Thu, Apr 22, 2010 at 11:50 PM, Arjun <arjunsingri at gmail.com>
wrote:
>> Personally, I would make everything a FunctionPass.
>
> What if a FunctionPass requires the results of a LoopPass? Is there a way
to get
> all loops of a function without using LoopPass and LoopInfo?
A LoopPass operates on loops. It updates/deletes loops. Its end result
is modified loops.
A FunctionPass operates on entire function.

LoopInfo is a FunctionPass that collect loops from a function. A
FunctionPass can certainly request another FunctionPass such as
LoopInfo.
-
Devang

But is there a better way of getting the loops in a function than using
LoopInfo? For some tasks it is necessary that we don't process the same loop
twice. Doing that with LoopInfo requires the use of a flag.

On Fri, Apr 23, 2010 at 12:41 PM, Devang Patel <devang.patel at
gmail.com>wrote:
> On Thu, Apr 22, 2010 at 11:50 PM, Arjun <arjunsingri at gmail.com>
wrote:
> >> Personally, I would make everything a FunctionPass.
> >
> > What if a FunctionPass requires the results of a LoopPass? Is there a
way
> to get
> > all loops of a function without using LoopPass and LoopInfo?
>
> A LoopPass operates on loops. It updates/deletes loops. Its end result
> is modified loops.
> A FunctionPass operates on entire function.
>
> LoopInfo is a FunctionPass that collect loops from a function. A
> FunctionPass can certainly request another FunctionPass such as
> LoopInfo.
> -
> Devang
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20100424/0976f3a7/attachment.html>