This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug target/32086] [4.3 Regression] 10% to 20% Performance Regression Between 4.1.3 and 4.3



------- Comment #12 from dominiq at lps dot ens dot fr  2007-12-10 16:03 -------
> committed, cost model now enabled for i386.

Is it working for Intel Core2Duo? At revision 130743 and

Using built-in specs.
Target: i686-apple-darwin9
Configured with: ../gcc-4.3-work/configure --prefix=/opt/gcc/gcc4.3w
--mandir=/opt/gcc/gcc4.3w/share/man --infodir=/opt/gcc/gcc4.3w/share/info
--build=i686-apple-darwin9 --enable-languages=c,c++,fortran,objc,obj-c++,java
--with-gmp=/sw --with-libiconv-prefix=/sw --with-system-zlib
--x-includes=/usr/X11R6/include --x-libraries=/usr/X11R6/lib
Thread model: posix
gcc version 4.3.0 20071210 (experimental) (GCC) 

for 'gfc -O3 -ffast-math -funroll-loops induct.f90' (with/without
-fvect-cost-model), the execution time is:

93.986u 0.051s 1:34.04 99.9%    0+0k 0+0io 0pf+0w

while for 'gfc -O3 -ffast-math -funroll-loops --param min-vect-loop-bound=2
induct.f90', it is:

76.345u 0.048s 1:16.39 99.9%    0+0k 0+0io 0pf+0w

If yes, the cost model should be tuned for Core2Duo. If no, did I do something
wrong with the configure?

Should I open a new PR for these questions?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32086


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]