For the induct.f90 test case from the polyhedron test suite, I get the
following timings (revision 130990):
[ibook-dhum] lin/source% time gfc -O3 -ffast-math -funroll-loops induct.f90
11.226u 0.496s 0:12.42 94.2% 0+0k 0+54io 15pf+0w
[ibook-dhum] lin/source% time a.out > tmp
91.148u 0.092s 1:31.27 99.9% 0+0k 0+9io 12pf+0w
[ibook-dhum] lin/source% time gfc -O3 -ffast-math -funroll-loops --param
min-vect-loop-bound=1 induct.f90
11.205u 0.492s 0:11.84 98.7% 0+0k 0+27io 0pf+0w
[ibook-dhum] lin/source% time a.out > tmp
91.145u 0.096s 1:31.24 99.9% 0+0k 0+4io 0pf+0w
[ibook-dhum] lin/source% time gfc -O3 -ffast-math -funroll-loops --param
min-vect-loop-bound=2 induct.f90
11.101u 0.491s 0:11.78 98.3% 0+0k 0+17io 0pf+0w
[ibook-dhum] lin/source% time a.out > tmp
73.596u 0.054s 1:13.65 99.9% 0+0k 0+9io 0pf+0w
Am I correct to understand that for this revisions -O3 implies
vectorization+cost_model?
If yes, it seems that the cost model should be tuned for the Intel Core2Duo.
--
Summary: The vector cost model does not seem suited for Intel
Core2Duo
Product: gcc
Version: 4.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dominiq at lps dot ens dot fr
GCC build triplet: i686-apple-darwin9
GCC host triplet: i686-apple-darwin9
GCC target triplet: i686-apple-darwin9
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34501
