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] Accepts non-matching invalid dummy procedure as actual argument
Date: Tue, 16 Jul 2013 06:24:00 -0000	[thread overview]
Message-ID: <bug-57711-4-cUngfpsKq3@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

--- Comment #6 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Patch for PR40276 and this PR:
http://gcc.gnu.org/ml/fortran/2013-06/msg00132.html (approved).

It fails for the test case http://gcc.gnu.org/ml/fortran/2013-07/msg00017.html
(-> PR39290 and PR20896). In that test case, "s1" and "s2" are ambiguous in
F2003/F2008.

However, I fear that the check in the patch above will give a bogus error for
  interface gen
    subroutine s1(x)
      real, external :: x
    end subroutine s1
    subroutine s1(x)
      integer, external :: x
    end subroutine s1
  end interface
which is valid since F2008 ("both data objects or known to be functions, and
neither is TKR compatible with the other,", 12.4.3.4.5). The issue does not
occur yet, as the feature is not yet implemented.


      parent reply	other threads:[~2013-07-16  6:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-25 17:51 [Bug fortran/57711] New: Fortran 4.7.2/4.8.1 error: constraints for functions parameters 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
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 [this message]

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-cUngfpsKq3@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: link
Be 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).