public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/55593] [4.8 Regression] Bogus error on passing DO LOOP variable Date: Thu, 06 Dec 2012 22:02:00 -0000 [thread overview] Message-ID: <bug-55593-4-fXeplXN7aZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55593-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55593 --- Comment #2 from Thomas Koenig <tkoenig at gcc dot gnu.org> 2012-12-06 22:02:01 UTC --- (In reply to comment #1) > From frontend-passes.c's doloop_code > > case EXEC_CALL: > f = co->symtree->n.sym->formal; > > I think one should use in this case > co->value.function.esym > > I believe co->value.function.* should always exist, Not for a subroutine call ;-) The following patch seems to work: Index: frontend-passes.c =================================================================== --- frontend-passes.c (Revision 193793) +++ frontend-passes.c (Arbeitskopie) @@ -1277,8 +1277,12 @@ doloop_code (gfc_code **c, int *walk_subtrees ATTR break; case EXEC_CALL: - f = co->symtree->n.sym->formal; + if (co->resolved_sym == NULL) + break; + + f = co->resolved_sym->formal; + /* Withot a formal arglist, there is only unknown INTENT, which we don't check for. */ if (f == NULL) > given that it comes after > resolution (if not, the symtree can be used as fall back). In any case, one > needs to be careful if it isn't an "isym" instead. This is checked for in the code already. I could not come up with a test case which fails for a function, so I don't think this regression also applies to generic function calls.
next prev parent reply other threads:[~2012-12-06 22:02 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-12-04 13:10 [Bug fortran/55593] New: " sfilippone at uniroma2 dot it 2012-12-04 14:50 ` [Bug fortran/55593] [4.8 Regression] " burnus at gcc dot gnu.org 2012-12-06 22:02 ` tkoenig at gcc dot gnu.org [this message] 2012-12-09 9:15 ` tkoenig at gcc dot gnu.org 2012-12-09 9:17 ` tkoenig 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-55593-4-fXeplXN7aZ@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).