------- Comment #6 from janus at gcc dot gnu dot org 2010-03-05 09:36 ------- (In reply to comment #5) > All of these throw error messages like > > ABSTRACT INTERFACE '...' must not be referenced at (1)
This was PR41873 and was fixed by querying "expr->value.function.name", which fails now. We should find a better way to silence this error message for polymorphic calls. > Type mismatch in argument '...' at (1); passed CLASS(...) to CLASS(...) This one is a bit more tricky, but understandable. It is not a problem of the one-line patch shown above, but of the implementation of polymorphic calls: When doing a polymorphic call with 'dynamic type /= declared type' of the passed object and an overridden TBP, we have to convert the passed object to a CLASS of the dynamic type. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43256