http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47692
--- Comment #11 from John T <jrt at worldlinc dot net> 2011-02-16 01:19:36 UTC --- (In reply to comment #8) > On Fri, Feb 11, 2011 at 07:56:05PM +0000, jrt at worldlinc dot net wrote: > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47692 > > > > --- Comment #6 from John T <jrt at worldlinc dot net> 2011-02-11 19:56:02 > > UTC --- > > I built the reference BLAS included with Lapack from source. I just got the > > results from blas_testing using gcc-4.4.5 and results good again. I don't > > know > > where to find the raw results from lapack and blas testing. Should there be > > an > > ieee flag in compiler settings? Any flags on how to round? > > > > My flags were: > > # > > FORTRAN = gfortran -fimplicit-none -g > > OPTS = -O3 > > DRVOPTS = $(OPTS) > > NOOPT = -g -O0 > > LOADER = gfortran -g > > LOADOPTS = > > > > I just built the blas included with lapack-3.3.0 with > -O3 of x86_64-*-freebsd with 4.5.3 and 4.6.0 (a fews > old version). There were no errors. Can you rebuild > with -O and see if you have problems? If you have > problems with -O, can you then use -O0 -ffloat-store? I haven't been able to try these suggestions because I'm finding a different problem, linking. The GCC programs didn't respond well to an attempt to reconfigure the existing build so I rebuilt for /usr/local and used a colorgcc trick to switch between 4.4.5 and the test version. But the build for /usr/local tried to link with /usr/lib/libgfortran.so.3 and the first set of test programs (in lapack-3.3.0/INSTALL) wouldn't run. I don't see anything in the makefiles that would confuse a linker.
