public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "andy at gwentswordclub dot co.uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/58099] over-zealous Error pointer error checking in gfortran 4.8
Date: Wed, 07 Aug 2013 08:48:00 -0000 [thread overview]
Message-ID: <bug-58099-4-PtHUKjG0u2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58099-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58099
Andrew McLeod <andy at gwentswordclub dot co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |andy at gwentswordclub dot co.uk
--- Comment #2 from Andrew McLeod <andy at gwentswordclub dot co.uk> ---
Seems to be explicitly permitted by the Fortran 2003 (at least draft) standard?
Section 7.4.2.2
...
If proc-pointer-object has an explicit interface, its characteristics shall be
the same as proc-target except that proc-target may be pure even if
proc-pointer-object is not pure and proc-target may be an elemental intrinsic
procedure even if proc-pointer-object is not elemental.
...
(although non-intrinsic elemental procedures are not allowed for some reason).
next prev parent reply other threads:[~2013-08-07 8:48 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 6:12 [Bug fortran/58099] New: " daniel.price at monash dot edu
2013-08-07 6:14 ` [Bug fortran/58099] " daniel.price at monash dot edu
2013-08-07 8:48 ` andy at gwentswordclub dot co.uk [this message]
2013-08-07 9:03 ` [Bug fortran/58099] [F03] over-zealous procedure " janus at gcc dot gnu.org
2013-08-07 9:13 ` andy at gwentswordclub dot co.uk
2013-08-07 9:26 ` [Bug fortran/58099] [4.8/4.9 Regression] [F03] over-zealous procedure-pointer error checking janus at gcc dot gnu.org
2013-08-07 9:35 ` janus at gcc dot gnu.org
2013-08-07 12:17 ` janus at gcc dot gnu.org
2013-08-08 7:25 ` burnus at gcc dot gnu.org
2013-08-08 7:42 ` janus at gcc dot gnu.org
2013-08-10 12:57 ` janus at gcc dot gnu.org
2013-08-16 15:29 ` jakub at gcc dot gnu.org
2013-09-20 6:22 ` burnus at gcc dot gnu.org
2013-09-20 7:44 ` janus at gcc dot gnu.org
2013-09-20 8:25 ` janus at gcc dot gnu.org
2013-09-20 8:28 ` janus at gcc dot gnu.org
2013-09-20 9:13 ` janus at gcc dot gnu.org
2013-09-20 10:38 ` janus at gcc dot gnu.org
2013-09-20 10:44 ` janus at gcc dot gnu.org
2013-10-16 9:51 ` jakub at gcc dot gnu.org
2013-10-17 6:22 ` burnus at gcc dot gnu.org
2013-11-16 23:13 ` janus at gcc dot gnu.org
2013-11-17 12:14 ` janus at gcc dot gnu.org
2013-11-17 13:46 ` janus at gcc dot gnu.org
2013-12-02 22:10 ` burnus at gcc dot gnu.org
2013-12-03 23:03 ` burnus at gcc dot gnu.org
2013-12-08 21:34 ` burnus at gcc dot gnu.org
2013-12-08 21:42 ` burnus at gcc dot gnu.org
2013-12-08 23:56 ` daniel.price at monash dot edu
2013-12-09 23:17 ` 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-58099-4-PtHUKjG0u2@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).