Polyhedron benchmark results on AMD64

[Dorit Nuzman]

> Contrary to you I used -ftree-vectorize which seems to make things
> faster, but breaks two g95 tests.
>

which tests? is there a PR open for this?

thanks,
dorit

> [sunf95]
> > I especially wonder how they do get fatigue so fast...
> This is indeed a good question, especially since they don't use sincos
> (which ifort and newer gfortran 4.3 use). Pathscale is even faster!
>
> gfortran can improve by ~25% using one of Richard's patches, I think it
> is the following patch:
> http://gcc.gnu.org/ml/gcc-patches/2007-01/msg02335.html
>
> In addition, I think we can gain a bit more by vectorizing sincos (it is
> not yet vectorized, if I understood Richard correctly).
>
> Actually, one of the problems of gfortran is that we create much too
> many temporary variables in the middle end as Richard mentioned
> recently. --- Has anyone actually looked at his patch at
> http://gcc.gnu.org/ml/fortran/2007-02/msg00132.html
>
> > Feel free to comment or suggest other ideas. I'd also be interested in
> > OpenMP benchmarks, although I've not yet found if there's any such
> > benchmark suite available freely.
> Well, there is a OpenMP validation suite available, but this is not
> really a benchmark:
> http://www.hlrs.de/organization/amt/projects/openmpvalidation/
> (I think the version on the webpage is slightly outdated, however.
> gfortran passes all tests.)
>
> Tobias
>