public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/40591] New: Procedure(interface): Rejected if interface is indirectly hostassociated Date: Mon, 29 Jun 2009 17:07:00 -0000 [thread overview] Message-ID: <bug-40591-13404@http.gcc.gnu.org/bugzilla/> (raw) The following program fails with: procedure(sub), pointer :: pptr2 1 Error: Interface 'sub' of procedure 'pptr2' at (1) must be explicit The question is whether it is valid or not. As both NAG f95 and ifort reject it (g95 accepts it), it might be invalid. However, if one uncomments pptr1: gfortran, NAG f95 and g95 accept pptr1 and pptr2 -- while ifort continues to reject pptr2 only. Thus it might be valid at the end. program main ! procedure(sub), pointer :: pptr1 ! nullify (pptr1) contains subroutine test() procedure(sub), pointer :: pptr2 nullify (pptr2) end subroutine test subroutine sub() end subroutine sub end program main -- Summary: Procedure(interface): Rejected if interface is indirectly hostassociated Product: gcc Version: 4.5.0 Status: UNCONFIRMED Keywords: rejects-valid Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: burnus at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40591
next reply other threads:[~2009-06-29 17:07 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-06-29 17:07 burnus at gcc dot gnu dot org [this message] 2009-07-07 5:01 ` [Bug fortran/40591] " pault at gcc dot gnu dot org 2009-07-08 4:38 ` pault at gcc dot gnu dot org 2009-07-08 9:48 ` pault at gcc dot gnu dot org 2009-07-08 11:47 ` dominiq at lps dot ens dot fr 2009-07-08 12:37 ` burnus at gcc dot gnu dot org 2009-07-08 13:28 ` pault at gcc dot gnu dot org 2009-07-08 13:31 ` dominiq at lps dot ens dot fr 2009-07-20 9:24 ` janus at gcc dot gnu dot org 2010-05-07 20:31 ` dfranke at gcc dot gnu dot org 2010-05-08 14:06 ` pault at gcc dot gnu dot org 2010-07-10 16:46 ` pault at gcc dot gnu dot 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-40591-13404@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: linkBe 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).