http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50684
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |4.6.2
--- Comment #4 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-10-12
20:54:58 UTC ---
(In reply to comment #3)
> TYPE MY_TYPE
> INTEGER, ALLOCATABLE :: VALUE
> END TYPE
> type(MY_TYPE), intent(in) :: dt
> call move_alloc(dt%VALUE, lv)
>
> This was rejected before, and still is with my patch.
But should it be rejected? move_alloc does not modify the association status of
"dt" - just of "dt%VALUE". Thus, I believe this test case is valid and, hence,
gfortran should not reject it.
(For what it is worth: gfortran 4.5, pgi 11.5-0 and crayftn 7.1.4.111 accept
the program, while gfortran 4.6/4.7 and ifort 11.1 reject it.)
