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/37222] [OOP] Checks when overriding type-bound procedures are incomplete
Date: Sat, 10 Sep 2011 15:22:00 -0000 [thread overview]
Message-ID: <bug-37222-4-V00qmnuvwm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-37222-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37222
janus at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|rejects-valid |
Summary|Checks when overriding |[OOP] Checks when
|type-bound procedures are |overriding type-bound
|incomplete |procedures are incomplete
--- Comment #1 from janus at gcc dot gnu.org 2011-09-10 15:02:33 UTC ---
(In reply to comment #0)
> At the moment, only gfc_compare_types is called; among the items that fail to
> be checked are rank, array shape (if known), ALLOCATABLE/POINTER attributes and
> INTENT declarations.
There are a few related PRs:
* for the INTENT check there is PR47978
* PR35831 concerns the shape check (originally for dummy procedure arguments,
but it applies to TBP overriding in the same way)
This PR can be used to track some of the missing checks:
* ALLOCATABLE/POINTER
* string length
* ...
next parent reply other threads:[~2011-09-10 15:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-37222-4@http.gcc.gnu.org/bugzilla/>
2011-09-10 15:22 ` janus at gcc dot gnu.org [this message]
2011-09-11 20:49 ` janus at gcc dot gnu.org
2013-12-10 21:56 ` 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-37222-4-V00qmnuvwm@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).