On Thu, Feb 07, 2013 at 07:51:20PM +0100, Duncan Sands wrote:
> Hi Vladimir, thanks for these numbers.
>
> ...
>> Therefore I had to use *Dragonegg* (a GCC plugin which uses LLVM
>> backend instead of GCC backend) for generation of Fortran benchmarks
>> by LLVM.
> ...
>> I believe such progress is achieved mostly because of a *new RA*
>> introduced in LLVM 3.0 and *auto-vectorization*.
>
> I don't think it can be auto-vectorization, because I forgot to turn on the
> LLVM auto-vectorizer in dragonegg-3.2 (oops!).
>
Duncan,
I was under the impression that the vectorization in llvm 3.2 was still
rather experimental compared to the current state in llvm 3.3svn (where it is
now enabled for clang at -O3). Perhaps it would be more fruitful to compare
gcc trunk and llvm svn.
Jack
ps Regarding LTO, my understanding is that, at least for darwin, the LTO
in llvm is still primarily limited to dead-code elimination. When I last
asked about this, Chris Lattner said that they felt more was to be gained
from improving the IPA in the compiler than implementing the rest of LTO. Of
course that was a couple years back.
> Ciao, Duncan.
