public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/54147] [F03] Interface checks for PPCs & TBPs
Date: Tue, 31 Jul 2012 20:43:00 -0000	[thread overview]
Message-ID: <bug-54147-4-8QVCleTxUE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54147-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54147

--- Comment #2 from janus at gcc dot gnu.org 2012-07-31 20:43:16 UTC ---
For TBPs there seems to be a similar but non-equivalent check in
resolve_typebound_procedure. It is supposed to check for F08:C465, but
apparently is also applied to the interface of deferred procedures (which it
should not be), and therefore probably rejects too much (all four cases in
comment 1 are rejected).


  parent reply	other threads:[~2012-07-31 20:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-31 19:15 [Bug fortran/54147] New: " janus at gcc dot gnu.org
2012-07-31 20:36 ` [Bug fortran/54147] " janus at gcc dot gnu.org
2012-07-31 20:43 ` janus at gcc dot gnu.org [this message]
2012-08-01  9:34 ` [Bug fortran/54147] [F03] Interface checks for PPCs & deferred TBPs janus at gcc dot gnu.org
2012-08-02  8:58 ` janus at gcc dot gnu.org
2012-08-02  9:01 ` janus 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-54147-4-8QVCleTxUE@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).