------- Comment #10 from janus at gcc dot gnu dot org 2010-08-19 13:08 -------
(In reply to comment #9)
> (In reply to comment #4)
> > 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.
>
> 3) Do it in the original module (like in #2), but statically via default
> initialization.
Mine. I'm working on a patch which implements solution #3. It already fixes the
test case, but still has a few regresssions.
--
janus at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|unassigned at gcc dot gnu |janus at gcc dot gnu dot org
|dot org |
Status|NEW |ASSIGNED
Last reconfirmed|2010-08-13 08:22:22 |2010-08-19 13:08:47
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45271
