This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/47574] internal compiler error: in build2_stat, at tree.c:3795
- From: "dominiq at lps dot ens.fr" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 2 Feb 2011 09:35:33 +0000
- Subject: [Bug fortran/47574] internal compiler error: in build2_stat, at tree.c:3795
- Auto-submitted: auto-generated
- References: <bug-47574-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47574
--- Comment #8 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2011-02-02 09:35:31 UTC ---
(In reply to comment #6)
> I have used gdb for minimally, but what is its use here? I cannot create an
> executable if I do not reduce the optimization level. What do you suggest?
I suggest to run gdb on f951 to see the path leading to the error
exch2_uv_agrid_3d_rl.f:293:0: internal compiler error: in build2_stat, at
tree.c:3795
gfortran is located in /some_path/bin. You'll find f951 in
/some_path/libexec/gcc/platform/version/
(gdb /opt/gcc/gcc4.6w/libexec/gcc/x86_64-apple-darwin10.6.0/4.6.0/f951 for me).
Set a breakpoint to fancy_abort, run the code and do a backtrace.
(In reply to comment #7)
> What makes the problem go away is commenting out line 949.
There is no line 949 in attachment 23201. The goal is to reduce the file to the
"minimal" size reproducing the ICE. CALL and COMMON have triggered bugs in the
past, hence my question (note that in the attachment 23201 there are only two
COMMONs: /EEPARAMS_L/ and /EEPARAMS_I/).