This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/40005] segfault in gt_ggc_mx_lang_tree_node
- From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 3 May 2009 19:37:40 -0000
- Subject: [Bug fortran/40005] segfault in gt_ggc_mx_lang_tree_node
- References: <bug-40005-6642@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #8 from rguenth at gcc dot gnu dot org 2009-05-03 19:37 -------
This is not a new problem - our recursive GC manages to do this in some cases.
What helps sometimes is to adjust the way structures are linked to avoid too
deep recursion. Maybe the GFortran FE trees are not optimized for that?
Thus, the question is what are we recursing on here? type.next_variant
if my sources are matching yours (look at gt-fortran-f95-lang.h:337).
What type do we have so many variants of?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40005