------- Comment #3 from claumann at princeton dot edu 2007-08-30 18:40 -------
Subject: Re: [Regression 4.3] bus error compiling dqelg.f in scipy on intel
mac
Howdy-
Thanks for looking into it!
It compiles just fine with
gfortran -c dqelg.f
I'm not especially excited about trying to compile a newer version of
gfortran at the moment. Do OS X compiles go smoothly? I don't believe
that valgrind is available for OS X.
This gfortran is available as a binary. I actually downgraded teh
binary to 4.2 and managed to compile the code. I suppose I could've
just turned off optimizations as well..
I ran f951 in gdb for you with a backtrace. Don't know if it's
helpful but here's the output:
penguin:~/gcc-bug claumann$ gdb /opt/usr/local/libexec/gcc/i386-apple-
darwin8.10.1/4.3.0/f951 GNU gdb 6.3.50-20050815 (Apple version
gdb-573) (Fri Oct 20 15:50:43 GMT 2006)Copyright 2004 Free Software
Foundation, Inc.GDB is free software, covered by the GNU General
Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for
details.
This GDB was configured as "i386-apple-darwin"...Reading symbols for
shared libraries .... done
(gdb) r dqelg.f -ffixed-form -fPIC -quiet -dumpbase dqelg.f -mmacosx-
version-min=10.4 -mtune=generic -auxbase dqelg -O3 -version -
fintrinsic-modules-path /opt/usr/local/bin/../lib/gcc/i386-apple-
darwin8.10.1/4.3.0/finclude -o /var/tmp//cc3A8yuy.sStarting program: /
opt/usr/local/libexec/gcc/i386-apple-darwin8.10.1/4.3.0/f951 dqelg.f -
ffixed-form -fPIC -quiet -dumpbase dqelg.f -mmacosx-version-min=10.4 -
mtune=generic -auxbase dqelg -O3 -version -fintrinsic-modules-path /
opt/usr/local/bin/../lib/gcc/i386-apple-darwin8.10.1/4.3.0/finclude -
o /var/tmp//cc3A8yuy.s
Reading symbols for shared libraries .+ done
GNU F95 version 4.3.0 20070810 (experimental) (i386-apple-darwin8.10.1)
compiled by GNU C version 4.3.0 20070810 (experimental), GMP
version 4.2.1, MPFR version 2.2.1.
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_PROTECTION_FAILURE at address: 0x0000000c
build_classic_dist_vector_1 (ddr=0x434c3b20, ddr_a=0x0,
ddr_b=0x434af898, dist_v=0x7b4d8c, init_b=0x434e9bd0 "A",
index_carry=0x7) at ../../gcc-4.3-20070810/gcc/tree-data-ref.c:2719
2719 ../../gcc-4.3-20070810/gcc/tree-data-ref.c: No such file or
directory.
in ../../gcc-4.3-20070810/gcc/tree-data-ref.c
(gdb) bt
#0 build_classic_dist_vector_1 (ddr=0x434c3b20, ddr_a=0x0,
ddr_b=0x434af898, dist_v=0x7b4d8c, init_b=0x434e9bd0 "A",
index_carry=0x7) at ../../gcc-4.3-20070810/gcc/tree-data-ref.c:2719
#1 0xbfffef44 in ?? ()
Previous frame inner to this frame (corrupt stack?)
(gdb)
On Aug 30, 2007, at 12:12 PM, burnus at gcc dot gnu dot org wrote:
>
>
> ------- 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
>
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug, or are watching someone who is.
> You reported the bug, or are watching the reporter.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33250
