public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "anlauf at gmx dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/42353] New: [OOP] Bogus Error: Name 'vtype$...' at (1) is an ambiguous reference ... Date: Fri, 11 Dec 2009 22:53:00 -0000 [thread overview] Message-ID: <bug-42353-6318@http.gcc.gnu.org/bugzilla/> (raw) Hi there, the attached code compiles with nagfor but fails to do so with gfortran 4.5.0 rev. 155016: gfcbug96.f90:45.33: end module concrete_inner_product 1 Error: Name 'vtype$vector_class' at (1) is an ambiguous reference to 'vtype$vect or_class' from module 'concrete_vector' gfcbug96.f90:45.33: end module concrete_inner_product 1 Error: Name 'vtype$vector_class' at (1) is an ambiguous reference to 'vtype$vect or_class' from module 'concrete_vector' gfcbug96.f90:43.23: use concrete_gradient 1 Error: The element in the derived type constructor at (1), for pointer component '$extends', is DERIVED but should be DERIVED -- Summary: [OOP] Bogus Error: Name 'vtype$...' at (1) is an ambiguous reference ... Product: gcc Version: 4.5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: anlauf at gmx dot de http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42353
next reply other threads:[~2009-12-11 22:53 UTC|newest] Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-12-11 22:53 anlauf at gmx dot de [this message] 2009-12-11 22:54 ` [Bug fortran/42353] " anlauf at gmx dot de 2009-12-11 23:13 ` janus at gcc dot gnu dot org 2009-12-13 21:10 ` janus at gcc dot gnu dot org 2009-12-13 21:41 ` janus at gcc dot gnu dot org 2009-12-16 21:16 ` anlauf at gmx dot de 2009-12-17 21:09 ` anlauf at gmx dot de 2009-12-28 14:15 ` janus at gcc dot gnu dot org 2009-12-28 14:29 ` janus at gcc dot gnu dot org 2009-12-28 15:24 ` janus at gcc dot gnu dot org 2009-12-28 18:35 ` anlauf at gmx dot de 2009-12-28 19:13 ` janus at gcc dot gnu dot org 2009-12-28 21:44 ` anlauf at gmx dot de 2009-12-28 21:59 ` janus at gcc dot gnu dot org 2009-12-28 22:39 ` anlauf at gmx dot de 2009-12-28 23:13 ` janus at gcc dot gnu dot org 2009-12-28 23:16 ` janus at gcc dot gnu dot org 2009-12-30 17:35 ` [Bug fortran/42353] [fortran-dev] " janus at gcc dot gnu dot org 2010-01-09 23:11 ` jvdelisle at gcc dot gnu dot org 2010-01-09 23:21 ` dominiq at lps dot ens dot fr 2010-01-10 13:34 ` dominiq at lps dot ens dot fr 2010-01-18 22:18 ` anlauf at gmx dot de 2010-01-19 0:25 ` jvdelisle at gcc dot gnu dot org 2010-01-19 2:37 ` jvdelisle at gcc dot gnu dot org 2010-01-22 4:31 ` jvdelisle at gcc dot gnu dot org 2010-01-22 4:32 ` jvdelisle at gcc dot gnu dot org 2010-04-16 5:59 ` pault at gcc dot gnu dot org 2010-04-18 13:13 ` janus at gcc dot gnu dot org 2010-04-18 13:50 ` pault at gcc dot gnu dot org 2010-04-18 13:55 ` dominiq at lps dot ens dot fr 2010-04-18 17:24 ` pault at gcc dot gnu dot org 2010-04-18 17:26 ` pault at gcc dot gnu dot org 2010-04-18 17:29 ` pault at gcc dot gnu dot org 2010-04-18 17:29 ` pault at gcc dot gnu dot org 2010-04-29 19:12 ` pault 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=bug-42353-6318@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).