llvm-project/flang/test/Semantics/definable02.f90
Peter Klausler d5285fef00
[flang] Downgrade error message to a portability warning (#98368)
f18 current emits an error when an assignment is made to an array
section with a vector subscript, and the array is finalized with a
non-elemental final subroutine. Some other compilers emit this error
because (I think) they want variables to only be finalized in place, not
by a subroutine call involving copy-in & copy-out of the finalized
elements.

Since many other Fortran compilers can handle this case, and there's
nothing in the standards to preclude it, let's downgrade this error
message to a portability warning.

This patch got complicated because the API for the WhyNotDefinable()
utility routine was such that it would return a message only in error
cases, and there was no provision for returning non-fatal messages. It
now returns either nothing, a fatal message, or a non-fatal warning
message, and all of its call sites have been modified to cope.
2024-07-11 13:12:00 -07:00

45 lines
1.0 KiB
Fortran

! RUN: %python %S/test_errors.py %s %flang_fc1 -pedantic -Werror
! Ensure that FINAL subroutine can be called for array with vector-valued
! subscript.
module m
type t1
contains
final :: f1
end type
type t2
contains
final :: f2
end type
type t3
contains
final :: f3
end type
contains
subroutine f1(x)
type(t1), intent(in out) :: x(:)
end subroutine
subroutine f2(x)
type(t2), intent(in out) :: x(..)
end subroutine
impure elemental subroutine f3(x)
type(t3), intent(in out) :: x
end subroutine
end module
program test
use m
type(t1) x1(1)
type(t2) x2(1)
type(t3) x3(1)
x1(:) = [t1()] ! ok
x2(:) = [t2()] ! ok
x3(:) = [t3()] ! ok
!PORTABILITY: Variable 'x1([INTEGER(8)::1_8])' has a vector subscript and will be finalized by non-elemental subroutine 'f1'
x1([1]) = [t1()]
!PORTABILITY: Variable 'x2([INTEGER(8)::1_8])' has a vector subscript and will be finalized by non-elemental subroutine 'f2'
x2([1]) = [t2()]
x3([1]) = [t3()] ! ok
end