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/45961] New: [4.6 Regression] [OOP] Problem with polymorphic type-bound operators Date: Sun, 10 Oct 2010 10:04:00 -0000 [thread overview] Message-ID: <bug-45961-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45961 Summary: [4.6 Regression] [OOP] Problem with polymorphic type-bound operators Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: janus@gcc.gnu.org MODULE DAT_MOD TYPE :: DAT CONTAINS PROCEDURE :: LESS_THAN GENERIC :: OPERATOR (.LT.) => LESS_THAN END TYPE DAT CONTAINS LOGICAL FUNCTION LESS_THAN(A, B) CLASS (DAT), INTENT (IN) :: A, B LESS_THAN = .true. END FUNCTION LESS_THAN END MODULE DAT_MOD PROGRAM TEST USE DAT_MOD IMPLICIT NONE TYPE NODE CLASS (DAT), POINTER :: PT END TYPE NODE TYPE (NODE) :: NDA, NDB PRINT *, LST(NDA,NDB) CONTAINS LOGICAL FUNCTION LST(A, B) CLASS (NODE), INTENT (IN) :: A, B LST = A%PT .LT. B%PT END FUNCTION LST END $ gfortran-4.6 test.f90 test.f90:21.15: PRINT *, LST(NDA,NDB) 1 Error: Type mismatch in argument 'a' at (1); passed TYPE(node) to CLASS(dat) This means that for some reason the formal arguments of LST come out wrongly as CLASS(dat), while they are actually CLASS(node)!?! Originally reported by Mark Rashid at http://gcc.gnu.org/ml/fortran/2010-10/msg00104.html.
next reply other threads:[~2010-10-10 10:04 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-10-10 10:04 janus at gcc dot gnu.org [this message] 2010-10-10 11:04 ` [Bug fortran/45961] " janus at gcc dot gnu.org 2010-10-10 16:34 ` dominiq at lps dot ens.fr 2010-10-10 18:17 ` janus at gcc dot gnu.org 2010-10-10 21:35 ` janus at gcc dot gnu.org 2010-10-10 21:36 ` 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-45961-4@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).