https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77663
--- Comment #1 from vehre at gcc dot gnu.org --- Hi David, what SW did you use to find this? #1, #2, #4 are covered by a patch I am doing at the moment. I believe that the report for #3 is at least misleading. Because when the associated memory is NULL the token of the allocatable component has to be unset, too. I.e. it is invalid for allocatable components to be NULL while the associated token is set. Nevertheless did the report show a logic error. The token never would have been stored at the appropriate location, but would be lost. The patch to come fixes this, too (hopefully). Thanks for the report. Regards, Andre
