This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/45271] [OOP] Polymorphic code breaks when changing order of USE statements
- From: "janus at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 13 Aug 2010 09:50:00 -0000
- Subject: [Bug fortran/45271] [OOP] Polymorphic code breaks when changing order of USE statements
- References: <bug-45271-6318@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #4 from janus at gcc dot gnu dot org 2010-08-13 09:50 -------
The problem is the following:
We have two routines called 'my_assign' (in two different modules). When
initializing the vtabs in the main program, we happen to use the wrong one:
if (vtab$trivial_gradient_type.assign == 0B)
{
vtab$trivial_gradient_type.assign = my_assign;
}
Possible solutions:
1) Make sure we use the right symbol from the right module.
2) Do the vtab initialization inside the module that defines the class, i.e.
add a module procedure like 'vtab$trivial_gradient_type$init' which does it,
and call this from the main program. Then there is no name ambiguity.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45271