mirror of
https://github.com/llvm/llvm-project.git
synced 2025-04-17 03:36:37 +00:00
1c91d9bdea
Before emitting a warning message, code should check that the usage in question should be diagnosed by calling ShouldWarn(). A fair number of sites in the code do not, and can emit portability warnings unconditionally, which can confuse a user that hasn't asked for them (-pedantic) and isn't terribly concerned about portability *to* other compilers. Add calls to ShouldWarn() or IsEnabled() around messages that need them, and add -pedantic to tests that now require it to test their portability messages, and add more expected message lines to those tests when -pedantic causes other diagnostics to fire.
40 lines
1.0 KiB
Fortran
40 lines
1.0 KiB
Fortran
! RUN: %python %S/test_errors.py %s %flang_fc1 -pedantic
|
|
program p
|
|
!PORTABILITY: Name 'p' declared in a main program should not have the same name as the main program
|
|
integer :: p
|
|
end
|
|
module m
|
|
!PORTABILITY: Name 'm' declared in a module should not have the same name as the module
|
|
integer :: m
|
|
end
|
|
submodule(m) sm
|
|
!PORTABILITY: Name 'sm' declared in a submodule should not have the same name as the submodule
|
|
integer :: sm
|
|
end
|
|
block data bd
|
|
!PORTABILITY: Name 'bd' declared in a BLOCK DATA subprogram should not have the same name as the BLOCK DATA subprogram
|
|
type bd
|
|
end type
|
|
end
|
|
module m2
|
|
type :: t
|
|
end type
|
|
interface
|
|
subroutine s
|
|
!ERROR: Module 'm2' cannot USE itself
|
|
use m2, only: t
|
|
end subroutine
|
|
end interface
|
|
end module
|
|
subroutine s
|
|
!ERROR: 's' is already declared in this scoping unit
|
|
integer :: s
|
|
end
|
|
function f() result(res)
|
|
integer :: res
|
|
!ERROR: 'f' is already declared in this scoping unit
|
|
!ERROR: The type of 'f' has already been declared
|
|
real :: f
|
|
res = 1
|
|
end
|