dded0e4bb2
When a procedure is included by name in a generic (either with a procedure statement in a generic interface or with a generic statement) we can't immediately resolve it to a subprogram symbol. That is because the subprogram may be defined later in the specification part. Instead, collect the names (and whether they should be module procedures) and resolve them to symbols at the end of the specification part. Also detect duplicate names then. This is needed for module file reading as these forward references can occur there. Write generics to module file using generic statements. This allows us to include the access-spec. Original-commit: flang-compiler/f18@d11d002084 Reviewed-on: https://github.com/flang-compiler/f18/pull/132
36 lines
975 B
Fortran
36 lines
975 B
Fortran
! Copyright (c) 2018, NVIDIA CORPORATION. All rights reserved.
|
|
!
|
|
! Licensed under the Apache License, Version 2.0 (the "License");
|
|
! you may not use this file except in compliance with the License.
|
|
! You may obtain a copy of the License at
|
|
!
|
|
! http://www.apache.org/licenses/LICENSE-2.0
|
|
!
|
|
! Unless required by applicable law or agreed to in writing, software
|
|
! distributed under the License is distributed on an "AS IS" BASIS,
|
|
! WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
! See the License for the specific language governing permissions and
|
|
! limitations under the License.
|
|
|
|
module m
|
|
real :: var
|
|
interface i
|
|
!ERROR: 'var' is not a subprogram
|
|
procedure :: sub, var
|
|
!ERROR: Procedure 'bad' not found
|
|
procedure :: bad
|
|
end interface
|
|
contains
|
|
subroutine sub
|
|
end
|
|
end
|
|
|
|
subroutine s
|
|
interface i
|
|
!ERROR: 'sub' is not a module procedure
|
|
module procedure :: sub
|
|
end interface
|
|
contains
|
|
subroutine sub
|
|
end
|
|
end
|