public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jaydub66 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/35830] ICE with PROCEDURE(<interface>) containing array formal arguments Date: Mon, 07 Apr 2008 22:02:00 -0000 [thread overview] Message-ID: <20080407220155.12154.qmail@sourceware.org> (raw) In-Reply-To: <bug-35830-13404@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from jaydub66 at gmail dot com 2008-04-07 22:01 ------- Another thing I just noticed is that dummy procedures are currently not checked for being called with the right arguments (-> compare_actual_formal), e.g. in the above test case "call f([1,2,3])" could also be called with a different number of arguments like "call f(1,2)" without any error message. In fact this check is currently omitted for any procedure which has the EXTERNAL attribute (which includes all procedures declared via the "PROCEDURE()::" statement). But I guess this check should better be omitted only for procedures which have an implicit interface, right? This can be cured with the following patch: Index: gcc/fortran/interface.c =================================================================== --- gcc/fortran/interface.c (revision 133905) +++ gcc/fortran/interface.c (working copy) @@ -2419,8 +2419,7 @@ gfc_procedure_use (gfc_symbol *sym, gfc_ } } - if (sym->attr.external - || sym->attr.if_source == IFSRC_UNKNOWN) + if (sym->attr.if_source == IFSRC_UNKNOWN) { gfc_actual_arglist *a; for (a = *ap; a; a = a->next) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35830
next prev parent reply other threads:[~2008-04-07 22:02 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-04-05 8:14 [Bug fortran/35830] New: ICE with PROCEDURE(<interface>) burnus at gcc dot gnu dot org 2008-04-05 14:57 ` [Bug fortran/35830] ICE with PROCEDURE(<interface>) containing array formal arguments burnus at gcc dot gnu dot org 2008-04-05 18:03 ` jaydub66 at gmail dot com 2008-04-06 12:45 ` fxcoudert at gcc dot gnu dot org 2008-04-07 22:02 ` jaydub66 at gmail dot com [this message] 2008-04-08 8:37 ` burnus at gcc dot gnu dot org 2008-04-09 18:49 ` jaydub66 at gmail dot com 2008-05-15 21:49 ` jaydub66 at gmail dot com 2008-05-28 21:29 ` janus at gcc dot gnu dot org 2008-05-28 21:35 ` janus at gcc dot gnu dot org 2008-05-31 9:17 ` janus at gcc dot gnu dot org 2008-06-02 8:45 ` burnus at gcc dot gnu dot org 2008-06-07 17:04 ` burnus at gcc dot gnu dot org 2008-06-07 17:31 ` burnus at gcc dot gnu dot org 2008-06-07 17:44 ` burnus at gcc dot gnu dot org 2008-06-08 7:50 ` burnus at gcc dot gnu dot org 2008-06-08 7:50 ` burnus 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=20080407220155.12154.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).