fce3a66f5e
When the same name is USE-associated with two or more distinct ultimate symbols, and they are not both generic procedure interfaces, it's not an error unless the name is actually referenced in the scope. But when the scope is itself a module or submodule, our module files don't preserve the error for later diagnosis -- instead, the UseErrorDetails symbol that serves as a "poison pill" in case of later use is discarded when the module file is generated. So emit additional USE statements to the module file so that a UseErrorDetails symbol is created anew when the module file is read.
20 lines
756 B
Fortran
20 lines
756 B
Fortran
!RUN: rm -rf %t && mkdir -p %t
|
|
!RUN: %flang_fc1 -fsyntax-only -J%t %S/Inputs/modfile84.f90
|
|
!RUN: not %flang_fc1 -fsyntax-only -J%t %s 2>&1 | FileCheck %s
|
|
|
|
!CHECK: error: Reference to 'foo' is ambiguous
|
|
!CHECK: 'foo' was use-associated from module 'modfile84a'
|
|
!CHECK: 'foo' was use-associated from module 'modfile84b'
|
|
!CHECK: error: 'foo' is not a callable procedure
|
|
!CHECK: 'foo' is USE-associated with 'foo' in module 'modfile84ab'
|
|
!CHECK: error: Reference to 'bar' is ambiguous
|
|
!CHECK: 'bar' was use-associated from module 'modfile84a'
|
|
!CHECK: 'bar' was use-associated from module 'modfile84b'
|
|
!CHECK: error: 'bar' is not a callable procedure
|
|
!CHECK: 'bar' is USE-associated with 'bar' in module 'modfile84ab'
|
|
|
|
use modfile84AB
|
|
call foo()
|
|
call bar()
|
|
end
|