--- Comment #13 from jv244 at cam dot ac dot uk 2007-07-03 18:15 ---
looks like current mainline is much slower than ifort (300%) on this testcase
(on core2).
> ifort -xT -O2 test.f90
> ./a.out
0.000E+000
0.2280140 0.2280140
> gfortran -O3 -ffast-ma
--- Comment #12 from jvdelisle at gcc dot gnu dot org 2006-05-02 05:01
---
With:
$ gfc -v
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: ../main/configure --prefix=/home/jerry/gcc/usr
--enable-languages=c,fortran --disable-libmudflap
Thread model: posix
gcc version 4.2
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-07
07:24 ---
This seems to be fixed on the mainline at least for me:
gold:~>gfortran -O1 t.f90
gold:~>!./
./a.out ; ./a.out ; ./a.out
2.220446049250313E-016
1.626753 0.9908500
2.2204460
--
Bug 17088 depends on bug 13246, which changed state.
Bug 13246 Summary: [new-ra][meta-bug] new-ra related problems
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13246
What|Old Value |New Value
---
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-01-06
21:39 ---
Looks like to me the register allocator is f'ing up as on PPC (where there more
fp registers) -O2 is faster
(by a factor of 2) than -O1. It is also one of the reasons why new-ra could be
fucking up too.
--- Additional Comments From jv244 at cam dot ac dot uk 2005-01-06 21:30
---
(In reply to comment #8)
> On closer inspection this is not a new-ra bug, sorry Joost.
> Can you see how the numbers look for you today? Don't use new-ra, it is
> known to be very, very broken.
timings for -O1
--- Additional Comments From steven at gcc dot gnu dot org 2005-01-03
12:17 ---
On closer inspection this is not a new-ra bug, sorry Joost.
Can you see how the numbers look for you today? Don't use new-ra, it is
known to be very, very broken.
--
What|Removed
