http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57297
Mikael Morin <mikael at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |janus at gcc dot gnu.org
--- Comment #8 from Mikael Morin <mikael at gcc dot gnu.org> ---
(In reply to gretay from comment #7)
> This patch fixes the failure in this test, but causes ICE in some fortran
> tests on qemu for arm-none-eabi. For example:
>
> FAIL: gfortran.dg/auto_dealloc_2.f90 -O (internal compiler error)
>
I'll need the help from an OOP expert.
Janus, what is the rationale for using so many different types for class
containers? It confuses the middle-end when assigning class containers.
For example in the case:
class_ptr => class_target
class_ptr's container has type '__class_(blah)p' while class_target has type
'__class_(blah)', so we can't do the assignment.
However, even if the types are different the types' contents seems to be the
same, so they could be merged?
