public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "palott at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/52469] Defining function pointer interface
Date: Sat, 03 Mar 2012 16:35:00 -0000	[thread overview]
Message-ID: <bug-52469-4-6IN6dPIBeC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52469-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52469

--- Comment #1 from palott at gmail dot com 2012-03-03 16:35:14 UTC ---
Created attachment 26817
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26817
simple example defining a function pointer interface and calling function

Defining func interface and type in the module leads to gfortran error in
latest release. This example compiles fine in earlier releases. Inserting these
definitions within the program test_proc_ptr, works okay in both releases.

  pointer :: func
  interface
     function func (z)
        real :: func
        real, intent (in) :: z
     end function func
  end interface

  type Contains_f_ptr
     procedure (func), pointer, nopass :: my_f_ptr
  end type Contains_f_ptr


  reply	other threads:[~2012-03-03 16:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-03 16:32 [Bug fortran/52469] New: " palott at gmail dot com
2012-03-03 16:35 ` palott at gmail dot com [this message]
2012-03-04 22:38 ` [Bug fortran/52469] [4.6/4.7/4.8 Regression] " dominiq at lps dot ens.fr
2012-03-05  8:19 ` [Bug fortran/52469] [4.6/4.7/4.8 Regression] -fwhole-file bug: Wrong backend_decl for result of PPC function burnus at gcc dot gnu.org
2012-03-05 20:32 ` burnus at gcc dot gnu.org
2012-03-08 11:33 ` burnus at gcc dot gnu.org
2012-03-08 19:37 ` burnus at gcc dot gnu.org
2012-03-10  8:19 ` burnus at gcc dot gnu.org
2012-03-10  9:21 ` burnus at gcc dot gnu.org
2012-03-10  9:22 ` 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-52469-4-6IN6dPIBeC@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).