public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/40646] ICE assigning array return value from type-bound procedure Date: Sat, 04 Jul 2009 12:45:00 -0000 [thread overview] Message-ID: <20090704124514.883.qmail@sourceware.org> (raw) In-Reply-To: <bug-40646-13404@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from burnus at gcc dot gnu dot org 2009-07-04 12:45 ------- The problem is: gcc_assert (expr2->value.function.isym || (!comp && gfc_return_by_reference (expr2->value.function.esym) which assumes that "esym" is set. However, looking at resolve.c's resolve_compcall: e->value.function.esym = NULL; Daniel: Is there a special reason to set "esym" as NULL rather than using e->value.function.esym = e->value.compcall.tbp->u.specific->n.sym; One could also change the gcc_assert, however, I fear that the program assumes at several places that either isym or esym is set - even if it does not crash, it might cause problems if it is not available. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40646
next prev parent reply other threads:[~2009-07-04 12:45 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-07-04 7:50 [Bug fortran/40646] New: " burnus at gcc dot gnu dot org 2009-07-04 12:22 ` [Bug fortran/40646] " pault at gcc dot gnu dot org 2009-07-04 12:38 ` janus at gcc dot gnu dot org 2009-07-04 12:45 ` burnus at gcc dot gnu dot org [this message] 2009-07-04 14:11 ` janus at gcc dot gnu dot org 2009-07-05 19:14 ` pault at gcc dot gnu dot org 2009-07-06 7:37 ` [Bug fortran/40646] [F03] array-valued procedure pointer components janus at gcc dot gnu dot org 2009-07-09 14:07 ` janus at gcc dot gnu dot org 2009-07-10 12:25 ` janus at gcc dot gnu dot org 2009-07-13 13:42 ` janus at gcc dot gnu dot org 2009-07-13 13:45 ` janus at gcc dot gnu dot org 2009-07-13 16:58 ` dominiq at lps dot ens dot fr
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=20090704124514.883.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: 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).