[Bug fortran/52227] [OOP] TARGET attribute mishandled in polymorphic types

["paul.richard.thomas at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52227

--- Comment #3 from paul.richard.thomas at gmail dot com <paul.richard.thomas at gmail dot com> 2012-07-13 15:10:52 UTC ---
Hmmm!  OK - I guess that we need
class_pointer/class_target/class_allocatable attributes that are
retained by the symbol, rather than the container.

Cheers

Paul

PS I have to recover the steps between the last unlimited polymorphic
patch that I sent you and the present on, which does the job for
unlimited OOP but breaks something such that regressions run into the
hundreds.  I have stared at it for a couple of evenings but cannot see
what generates the problem.  If I do not see it by Sunday, I'll let
you take a look.

On 13 July 2012 15:17, burnus at gcc dot gnu.org
<gcc-bugzilla@gcc.gnu.org> wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52227
>
> Tobias Burnus <burnus at gcc dot gnu.org> changed:
>
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |janus at gcc dot gnu.org
>
> --- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-07-13 13:17:23 UTC ---
> I think we need so change class.c's gfc_build_class_symbol. It currently only
> handles pointer/allocatable plus a (co)rank.
>
> It seems to definitely lacks support for TARGET, judging by this PR, PR51610
> and PR53951. At least I fear that some wrong-code bug is lurking there if
> TARGET is not properly set.
>
> As written in comment 0, there might be other attributes which have to be taken
> into account, e.g. VOLATILE or ASYNCHRONUOUS.
>
> Recall that when adding letters to the type name, either the number of allowed
> characters has to change or the length part in the hashing, otherwise, names
> might get cropped.
>
> We should try to fix this issue soonish, as it is a nasty wrong-code issue
> (depending on the optimization and timing) and it affects the ABI!
>
> --
> Configure bugmail: http://gcc.gnu.org/bugzilla/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug.