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/50408] [4.6/4.7 regression] ICE in transfer_expr Date: Thu, 24 Nov 2011 22:39:00 -0000 [thread overview] Message-ID: <bug-50408-4-wIfMf4G8Bd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50408-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50408 --- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-11-24 22:13:06 UTC --- That a -fwhole-file regression, which became the default in 4.6. The work around is -fno-whole-file. The problem is in gfc_get_extern_function_decl: gfc_find_symbol (sym->name, gsym->ns, 0, &s); if (s && s->backend_decl) { sym->backend_decl = s->backend_decl; return sym->backend_decl; } The problem is that this does not set sym->ts.u.derived{,->components{,->next}}->backend_decl for BT_DERIVED/BT_CLASS; one might also need to update sym->ts.u.cl... for BT_CHARACTER. Note: There are more places in trans*.c which call gfc_find_gsymbol
next prev parent reply other threads:[~2011-11-24 22:13 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-09-15 8:36 [Bug fortran/50408] New: " zeccav at gmail dot com 2011-09-15 13:42 ` [Bug fortran/50408] " Joost.VandeVondele at pci dot uzh.ch 2011-11-08 23:05 ` [Bug fortran/50408] [4.6/4.7 regression] " fxcoudert at gcc dot gnu.org 2011-11-11 11:31 ` burnus at gcc dot gnu.org 2011-11-24 22:39 ` burnus at gcc dot gnu.org [this message] 2011-11-24 23:31 ` burnus at gcc dot gnu.org 2011-11-25 16:37 ` burnus at gcc dot gnu.org 2011-11-25 17:34 ` burnus at gcc dot gnu.org 2011-11-25 17:36 ` 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-50408-4-wIfMf4G8Bd@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).