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/63674] procedure pointer and non/pure procedure Date: Wed, 10 Dec 2014 22:12:00 -0000 [thread overview] Message-ID: <bug-63674-4-NSZyrLr2El@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63674-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63674 --- Comment #2 from janus at gcc dot gnu.org --- Test case for ordinary procedure pointers: module test interface function func_interface ( ) RESULT( reslt ) INTEGER :: reslt end function func_interface end interface contains function func_1 ( ) RESULT( reslt ) integer :: reslt reslt = 1 end function func_1 pure subroutine eval( reslt ) integer, intent(out) :: reslt procedure(func_interface), pointer :: f f=>func_1 reslt = f() ! reslt = func_1() end subroutine eval end module test program prog use test integer :: reslt call eval(reslt) write(*,*) reslt end program prog This gives the expected error message with 4.9 and trunk, which shows that the problem only occurs for PPCs.
next prev parent reply other threads:[~2014-12-10 22:12 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-10-29 11:59 [Bug fortran/63674] New: " valeryweber at hotmail dot com 2014-12-10 22:02 ` [Bug fortran/63674] " janus at gcc dot gnu.org 2014-12-10 22:12 ` janus at gcc dot gnu.org [this message] 2014-12-10 22:18 ` janus at gcc dot gnu.org 2014-12-14 9:33 ` [Bug fortran/63674] [F03] " janus at gcc dot gnu.org 2014-12-14 12:05 ` janus at gcc dot gnu.org 2014-12-14 12:07 ` janus at gcc dot gnu.org 2014-12-15 10:35 ` 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-63674-4-NSZyrLr2El@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).