[Bug fortran/53950] 1.5 times slowdown from 4.4.0 to 4.7.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53950 Richard Guenther changed: What|Removed |Added Target||*-mingw Status|UNCONFIRMED |WAITING Last reconfirmed||2012-07-13 Ever Confirmed|0 |1 --- Comment #1 from Richard Guenther 2012-07-13 10:47:58 UTC --- Are you building a 64bit or a 32bit executable? Are you sure this is not an effect of whoever provides random_number() or log()?
[Bug fortran/53950] 1.5 times slowdown from 4.4.0 to 4.7.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53950 --- Comment #2 from Yury Kapoyko 2012-07-13 10:52:27 UTC --- Both targets are 32 bit. Yes, after deeper profiling it seems a problem to be inside log/cos/random. For example, fragments from gprof: 4.4.0: cosf - self seconds 0.77 4.7.0: cosf - self seconds 0.94 and so on. Is there a way to fix it?
[Bug fortran/53950] 1.5 times slowdown from 4.4.0 to 4.7.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53950 Richard Guenther changed: What|Removed |Added Target|*-mingw |i?86-mingw --- Comment #3 from Richard Guenther 2012-07-13 11:00:46 UTC --- These functions are not part of GCC but eventually part of the mingw runtime, so I suggest to file a bug there.
[Bug fortran/53950] 1.5 times slowdown from 4.4.0 to 4.7.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53950 --- Comment #4 from Yury Kapoyko 2012-07-13 12:39:05 UTC --- I agree with you. This buf refers to mingw, I think, it could be closed. Unfortunately, real application slows down to 30 times! But it's very hard to "extract" bug from there because it is rather complicated and multi-threaded. Also I have no profilers for Windows except gprof which is useless here. Compiled on Fedora (GCC 4.6.3) application works fine. I assume that the problem is with libgfortran, because if I run old application (compiled with GCC 4.4.0), but with new gfortran.dll in PATH it works exactly as bad, as new one.
