"== Pipeline, run-time and other issues == 

 I gave this article a good refactoring and there are some edges yet. 

 * old vector machines are still in use and some simpler (embedded) processors are not as powerful as cutting-edge versions. This is why I said ""some times"". Feel free to re-phrase that, of course. 
 * some processors can detect repetition in the load/store pattern and automatically change from normal instructions to vector instructions and the dynamic vectorization in the paper you mention is really interesting, but I was trying to cover ""software"" vectorizations. In the text I explain that it's not ""vectorizing at run-time"" but actually ""choosing the vectorized version at run-time"". Maybe a better title for the topic is needed, but I can't think of one that is as ""catchy"" as that... ;) 
 * I'll add memory reference optimizations (induction, reduction, etc) too, but I've been busy with loop dependence analysis and normalized loop. 

    

 "