public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/53328] New: [OOP] Ambiguous check for type-bound GENERIC shall ignore PASSed arguments Date: Fri, 11 May 2012 21:36:00 -0000 [thread overview] Message-ID: <bug-53328-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53328 Bug #: 53328 Summary: [OOP] Ambiguous check for type-bound GENERIC shall ignore PASSed arguments Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Keywords: accepts-invalid, diagnostic Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: burnus@gcc.gnu.org CC: janus@gcc.gnu.org Based on a report by Rafik Zurob. Compile the following module - and then the following: use m type(t) :: x call x%gen(5) end Does the call invoke sub1 or sub2? Obviously, gfortran should ignore the PASSed argument for the generic resolution of type-bound procedures, when checking for ambiguity. The following code is invalid but accepted: module m type t contains procedure, pass(this) :: sub1 procedure, pass(this) :: sub2 generic :: gen => sub1, sub2 end type t contains subroutine sub1(x, this) integer :: i class(t) :: this end subroutine sub1 subroutine sub2 (this, y) integer :: i class(t) :: this end subroutine sub2 end module m
next reply other threads:[~2012-05-11 21:29 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-11 21:36 burnus at gcc dot gnu.org [this message] 2012-05-11 22:16 ` [Bug fortran/53328] " burnus at gcc dot gnu.org 2012-05-12 18:06 ` burnus at gcc dot gnu.org 2012-06-17 16:40 ` janus at gcc dot gnu.org 2012-06-22 21:06 ` janus at gcc dot gnu.org 2012-06-22 21:11 ` 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-53328-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).