--- Comment #14 from fkar at nemesis-project dot org 2006-10-28 02:07
---
(In reply to comment #13)
> Are you building slamch.f and dlamch.f with -O3 or even -O1?
> Don't. These files try to determine machine values (e.g.,
> epsilon). Optimization can give some really s
--- Comment #12 from fkar at nemesis-project dot org 2006-10-28 01:34
---
I used (on three different XP boxes) the source code as provided by netlib
http://www.netlib.org/lapack/lapack.tgz,
the latest gfortran binaries, namely
http://quatramaran.ens.fr/~coudert/gfortran/gfortran
--- Comment #10 from fkar at nemesis-project dot org 2006-10-27 23:39
---
Starting from
http://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html#Optimize-Options
I compiled both BLAS/LAPACK using the following compiler flags:
-fdefer-pop -fguess-branch-probability -fcprop-registers
--- Comment #9 from fkar at nemesis-project dot org 2006-10-27 22:29
---
I confirm that the same problem exists with -O1.
It might be a target problem (gfortran used comes from a mingw build, dated
2006-10-21 and linked as an installer in
http://gcc.gnu.org/wiki/GFortranBinaries). As
--- Comment #5 from fkar at nemesis-project dot org 2006-10-27 21:51
---
(In reply to comment #4)
> What compiler option did you use to compile BLAS and LAPACK?
It is mentioned on http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29621#c0:
1. Build blas:
gfortran -c BLAS_SRC\*.f
--- Comment #2 from fkar at nemesis-project dot org 2006-10-27 21:14
---
I just tried to submit a reduced test case. Please reconsider this bug with
these two cases (one linking with a Fortran program and one with a C/C++ one
0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: fkar at nemesis-project dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29621
