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 & deferred TBPs
Date: Wed, 01 Aug 2012 09:34:00 -0000	[thread overview]
Message-ID: <bug-54147-4-FMw1AttH8F@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

janus at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2012-08-01
         AssignedTo|unassigned at gcc dot       |janus at gcc dot gnu.org
                   |gnu.org                     |
            Summary|[F03] Interface checks for  |[F03] Interface checks for
                   |PPCs & TBPs                 |PPCs & deferred TBPs
     Ever Confirmed|0                           |1

--- Comment #3 from janus at gcc dot gnu.org 2012-08-01 09:34:15 UTC ---
(In reply to comment #0)
> After fixing PR 42418, I realized that the constraints in F08:C1216 apply also
> to
> 1) procedure-pointer components and
> 2) type-bound procedures,

to be precise, they only apply to *deferred* TBPs, since 'regular' ones do not
have an interface specification.

I'm working on a patch ...


  parent reply	other threads:[~2012-08-01  9:34 UTC|newest]

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