public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/42207] [OOP] Compile-time errors on typed allocation and pointer function result assignment
Date: Tue, 03 Aug 2010 15:31:00 -0000	[thread overview]
Message-ID: <20100803153132.22329.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42207-15301@http.gcc.gnu.org/bugzilla/>



------- Comment #15 from dominiq at lps dot ens dot fr  2010-08-03 15:31 -------
I don't know if this related to comment #14, but with the patch of comment #12
the errors for the test pr37425#0 has changed from

pr37425.f90:7.13:

    PROCEDURE :: assign_t_from_int
             1
Error: Non-polymorphic passed-object dummy argument of 'assign_t_from_int' at
(1)
pr37425.f90:8.13:

    PROCEDURE :: equals_t_int
             1
Error: Non-polymorphic passed-object dummy argument of 'equals_t_int' at (1)
pr37425.f90:22.31:

  LOGICAL FUNCTION equals_t_int (me, i)
                               1
Error: First argument of operator interface at (1) must be INTENT(IN)

to

pr37425.f90:7.13:

    PROCEDURE :: assign_t_from_int
             1
Error: Non-polymorphic passed-object dummy argument of 'assign_t_from_int' at
(1)
pr37425.f90:8.13:

    PROCEDURE :: equals_t_int
             1
Error: Non-polymorphic passed-object dummy argument of 'equals_t_int' at (1)
pr37425.f90:10.30:

    GENERIC :: OPERATOR(==) => equals_t_int
                              1
Error: Undefined specific binding 'equals_t_int' as target of GENERIC '==' at
(1)
pr37425.f90:9.31:

    GENERIC :: ASSIGNMENT(=) => assign_t_from_int
                               1
Error: Undefined specific binding 'assign_t_from_int' as target of GENERIC '='
at (1)


-- 


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


  parent reply	other threads:[~2010-08-03 15:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-28 18:14 [Bug fortran/42207] New: " damian at rouson dot net
2009-11-28 18:25 ` [Bug fortran/42207] " sfilippone at uniroma2 dot it
2009-11-28 20:18 ` dominiq at lps dot ens dot fr
2009-11-29  2:50 ` damian at rouson dot net
2009-11-29 12:31 ` [Bug fortran/42207] [OOP] " janus at gcc dot gnu dot org
2009-11-29 16:22 ` dominiq at lps dot ens dot fr
2009-11-30  0:52 ` damian at rouson dot net
2009-11-30  1:16 ` damian at rouson dot net
2010-08-03 10:03 ` burnus at gcc dot gnu dot org
2010-08-03 11:36 ` janus at gcc dot gnu dot org
2010-08-03 11:49 ` dominiq at lps dot ens dot fr
2010-08-03 11:51 ` burnus at gcc dot gnu dot org
2010-08-03 12:59 ` janus at gcc dot gnu dot org
2010-08-03 13:43 ` dominiq at lps dot ens dot fr
2010-08-03 14:31 ` mikael at gcc dot gnu dot org
2010-08-03 15:31 ` dominiq at lps dot ens dot fr [this message]
2010-08-03 16:32 ` janus at gcc dot gnu dot org
2010-08-03 18:08 ` dominiq at lps dot ens dot fr
2010-08-03 18:55 ` dominiq at lps dot ens dot fr
2010-08-04  7:31 ` janus at gcc dot gnu dot org
2010-08-04 19:49 ` janus at gcc dot gnu dot org
2010-08-04 20:01 ` janus 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=20100803153132.22329.qmail@sourceware.org \
    --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).