------- Comment #2 from burnus at gcc dot gnu dot org 2007-08-30 18:12 -------
(gfortran bugs are by definition not critical or major for GCC as a whole;
still the gfortran team tries to fix regressions as soon as possible.)
I cannot reproduce this problem with today's gfortran on
x86_64-unknown-linux-gnu - neither with -m32 nor with -m64.
Does it also crash if you simply run
gfortran -c dqelg.f
without -fPIC -O3 -funroll-loops ?
If you have valgrind, could you run gfortran's f951 through valgrind. (To find
the arguments of f951, run gfortran as normal, but pass the "-v" argument; in
the output there is a line which contains a pathname to f951; copy that line.)
If you don't, can you run f951 in gdb and post a backtrace?
Not that it will necessarily help, but it might do so: Could you try a newer
version of gfortran?
--
burnus at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |burnus at gcc dot gnu dot
| |org
Summary|bus error compiling dqelg.f |[Regression 4.3] bus error
|in scipy on intel mac |compiling dqelg.f in scipy
| |on intel mac
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33250
