[llvm-commits] [llvm-gcc-4.2] r55718 - /llvm-gcc-4.2/trunk/gcc/llvm-backend.cpp

[Chris Lattner]

On Sep 23, 2008, at 10:22 AM, Devang Patel wrote:

>>>
>>> Only one advantage is a small convenience to llvm developers. When  
>>> we are using -analyze or -print or intentionally running selected  
>>> pass for debugging/testing then you do not want PassManager to  
>>> annoy you. This is not a big deal, and I do not see any advantage  
>>> for end users.
>>
>> How would it be annoying?  I don't understand.  It is just an  
>> optimization to speed up the pass.
>
> OK.  I spent some time investigating this, now the big question is  
> "Where in the pass sequence ?"
>

I don't understand what you're asking?  You're asking where the always  
inline pass should go?  If so, "at the start of the pass manager".  We  
should do always inlining before anything else.  In fact, it is  
probably better to do always inlinling completely separately from  
normal inlining.

-Chris