public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/56500] [OOP] "IMPLICIT CLASS(...)" wrongly rejected
Date: Mon, 18 Mar 2013 12:17:00 -0000	[thread overview]
Message-ID: <bug-56500-4-zKZY1BjY6T@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56500-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #9 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2013-03-18 12:16:59 UTC ---
> Yes. I hope this variant should work better (regtesting now):

It "works better", but still has regressions:

[macbook] f90/bug% gfc /opt/gcc/work/gcc/testsuite/gfortran.dg/proc_ptr_36.f90
/opt/gcc/work/gcc/testsuite/gfortran.dg/proc_ptr_36.f90:26.6:

pp => sub2
      1
Error: Interface mismatch in procedure pointer assignment at (1): 'sub2' is not
a function
/opt/gcc/work/gcc/testsuite/gfortran.dg/proc_ptr_36.f90:29.7:

call s(pp, .true.)
       1
Error: Interface mismatch in dummy procedure 'ss' at (1): 'pp' is not a
subroutine
/opt/gcc/work/gcc/testsuite/gfortran.dg/proc_ptr_36.f90:33.7:

call s(pp, .false.)
       1
Error: Interface mismatch in dummy procedure 'ss' at (1): 'pp' is not a
subroutine


  parent reply	other threads:[~2013-03-18 12:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-01 18:07 [Bug fortran/56500] New: " burnus at gcc dot gnu.org
2013-03-02  0:07 ` [Bug fortran/56500] " burnus at gcc dot gnu.org
2013-03-17 12:55 ` janus at gcc dot gnu.org
2013-03-17 13:12 ` janus at gcc dot gnu.org
2013-03-17 16:00 ` janus at gcc dot gnu.org
2013-03-17 19:46 ` dominiq at lps dot ens.fr
2013-03-17 21:02 ` janus at gcc dot gnu.org
2013-03-17 21:30 ` dominiq at lps dot ens.fr
2013-03-17 22:38 ` janus at gcc dot gnu.org
2013-03-18 12:17 ` dominiq at lps dot ens.fr [this message]
2013-03-18 12:57 ` janus at gcc dot gnu.org
2013-04-01 15:34 ` 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-56500-4-zKZY1BjY6T@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).