https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69422
Paul Thomas <pault at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #3 from Paul Thomas <pault at gcc dot gnu.org> ---
(In reply to Paul Thomas from comment #2)
> Hmmm! This works if the pointer attribute is changed to allocatable. As
> reported, it generates:
>
This is precisely the point! There is no obligation for the processor to
automatically (re)allocate a pointer component, is there?
Changing the assignment to
allocate (X%P%Source, source = 'test string')
works as expected.
I'm sorry but this one is invalid. I suppose that a runtime warning along the
lines of that just introduced for assignment of scalars to unallocated,
allocatable arrays could be introduced but I am seriously unconvinced that we
should be doing this for pointers.
Cheers
Paul
