From: pertti.kellomaki@tut.fi   
      
   Tim Frink wrote:   
   >>> And if profiling might be exploited here.   
   >> I didn't get you there i.e. profiling doesn't seem related to   
   >> pipelining as described above.   
   >   
   > This was just a question if it would make sense to somehow   
   > combine software pipelining with the most frequently executed   
   > path (determined by profiling). I can't imagine any useful   
   > combination of these two techniques, but maybe there are some?   
      
   Software pipelining does not provide much performance   
   increase for loops with low trip counts, but it increases   
   code size. So using it anywhere else but in the frequently   
   executed paths would be rather ill adviced. Profiling is a   
   good way to find those paths.   
   --   
   Pertti   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)