public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/40005] segfault in gt_ggc_mx_lang_tree_node
Date: Sun, 03 May 2009 19:37:00 -0000 [thread overview]
Message-ID: <20090503193740.21422.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40005-6642@http.gcc.gnu.org/bugzilla/>
------- 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
next prev parent reply other threads:[~2009-05-03 19:37 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-02 12:14 [Bug fortran/40005] New: " jv244 at cam dot ac dot uk
2009-05-02 12:22 ` [Bug fortran/40005] " jv244 at cam dot ac dot uk
2009-05-02 12:43 ` jv244 at cam dot ac dot uk
2009-05-02 13:44 ` jv244 at cam dot ac dot uk
2009-05-03 17:15 ` pault at gcc dot gnu dot org
2009-05-03 17:52 ` rguenth at gcc dot gnu dot org
2009-05-03 18:59 ` jv244 at cam dot ac dot uk
2009-05-03 19:14 ` jv244 at cam dot ac dot uk
2009-05-03 19:37 ` rguenth at gcc dot gnu dot org [this message]
2009-05-04 4:39 ` jv244 at cam dot ac dot uk
2009-05-04 7:12 ` jv244 at cam dot ac dot uk
2009-05-04 7:49 ` jv244 at cam dot ac dot uk
2009-05-05 20:45 ` pinskia at gcc dot gnu dot org
2009-05-05 20:48 ` pinskia at gcc dot gnu dot org
2009-05-06 4:37 ` jv244 at cam dot ac dot uk
2009-05-07 14:32 ` jv244 at cam dot ac dot uk
2009-05-09 14:57 ` jv244 at cam dot ac dot uk
2009-05-29 3:00 ` pinskia at gcc dot gnu dot org
2009-06-20 17:37 ` jv244 at cam dot ac dot uk
2009-07-21 7:54 ` jv244 at cam dot ac dot uk
2009-07-24 11:56 ` rguenth at gcc dot gnu dot org
2009-07-24 12:28 ` jv244 at cam dot ac dot uk
2009-07-24 15:33 ` rguenth at gcc dot gnu dot org
2009-07-24 15:43 ` jv244 at cam dot ac dot uk
2009-07-24 15:46 ` rguenth at gcc dot gnu dot org
2009-07-24 15:54 ` rguenth at gcc dot gnu dot org
2009-07-24 16:04 ` jv244 at cam dot ac dot uk
2009-07-24 16:05 ` jv244 at cam dot ac dot uk
2009-07-24 16:13 ` rguenth at gcc dot gnu dot org
2009-07-24 16:48 ` jv244 at cam dot ac dot uk
2009-07-24 16:51 ` rguenth at gcc dot gnu dot org
2009-07-24 16:57 ` jv244 at cam dot ac dot uk
2009-07-24 17:00 ` jv244 at cam dot ac dot uk
2009-07-24 17:14 ` rguenth at gcc dot gnu dot org
2009-07-24 17:31 ` jv244 at cam dot ac dot uk
2009-07-24 19:14 ` rguenth at gcc dot gnu dot org
2009-07-25 11:03 ` jv244 at cam dot ac dot uk
2009-07-25 11:12 ` rguenth at gcc dot gnu dot org
2009-07-25 13:45 ` rguenth at gcc dot gnu dot org
2009-07-25 13:45 ` rguenth at gcc dot gnu dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090503193740.21422.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).