public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/58356] ICE with finalization and type extension Date: Sun, 15 Sep 2013 11:41:00 -0000 [thread overview] Message-ID: <bug-58356-4-jrn7PXlUhD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-58356-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58356 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |ice-on-valid-code CC| |burnus at gcc dot gnu.org --- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> --- Segfaults at: at ../../gcc/fortran/class.c:1884 1884 if (fini->proc_tree->n.sym->attr.elemental) The problem is that fini != NULL but fini->proc_tree == NULL. Note that: fini->proc_sym->name is available with the name cfld
next prev parent reply other threads:[~2013-09-15 11:41 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-09-07 20:20 [Bug fortran/58356] New: " abensonca at gmail dot com 2013-09-15 11:41 ` burnus at gcc dot gnu.org [this message] 2013-09-15 12:09 ` [Bug fortran/58356] " dominiq at lps dot ens.fr 2013-09-16 18:02 ` burnus at gcc dot gnu.org 2013-09-16 18:02 ` burnus at gcc dot gnu.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=bug-58356-4-jrn7PXlUhD@http.gcc.gnu.org/bugzilla/ \ --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: linkBe 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).