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/57711] Fortran 4.7.2/4.8.1 error: constraints for functions parameters Date: Wed, 26 Jun 2013 06:11:00 -0000 [thread overview] Message-ID: <bug-57711-4-xnmbITQS22@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-57711-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57711 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |burnus at gcc dot gnu.org --- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> --- First, you have a *serious* bug in JAC/DUMMY_JAC: Namely, in DUMMY_JAC you have: double precision, intent(inout) :: RPAR(:) integer, intent(inout) :: IPAR(:) (Those have ASSUMED-SHAPE arrays) And in JAC: DOUBLE PRECISION, INTENT(INOUT) :: RPAR(*) INTEGER, INTENT(INOUT) :: IPAR(*) (And those are ASSUMED-SIZE arrays.) But for procedures declarations and its interface declarations, either both or neither has to use assumed-shape arrays. The compilers passes (internally) arguments quite differently - thus (unless the compiler detects it) it will cause problems at run time. Secondly and regrading gfortran: * For some reasons, it compiles with GCC 4.7 if one calls D_VODE instead of VODE. * The error message for generic matching should be better (cf. PR40276). When checking the interface of dummy procedure, it should be possible to give always an error.
next prev parent reply other threads:[~2013-06-26 6:11 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-06-25 17:51 [Bug fortran/57711] New: " kabanovdmitry at gmail dot com 2013-06-25 21:39 ` [Bug fortran/57711] " dominiq at lps dot ens.fr 2013-06-26 6:11 ` burnus at gcc dot gnu.org [this message] 2013-06-26 7:49 ` [Bug fortran/57711] Accepts non-matching invalid dummy procedure as actual argument burnus at gcc dot gnu.org 2013-06-26 13:56 ` kabanovdmitry at gmail dot com 2013-06-26 14:43 ` burnus at gcc dot gnu.org 2013-07-16 6:24 ` 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-57711-4-xnmbITQS22@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).