Files
clang-p2996/flang/test/Semantics/bind-c02.f90
Peter Klausler 1c91d9bdea [flang] Ensure that portability warnings are conditional (#71857)
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.
2023-11-13 16:13:50 -08:00

50 lines
1.3 KiB
Fortran

! RUN: %python %S/test_errors.py %s %flang_fc1 -pedantic
! Check for 8.6.4(1)
! The BIND statement specifies the BIND attribute for a list of variables and
! common blocks.
module m
interface
subroutine proc()
end
end interface
procedure(proc) :: pc1
!ERROR: Only variable and named common block can be in BIND statement
bind(c) :: proc
!ERROR: Only variable and named common block can be in BIND statement
bind(c) :: pc1
!ERROR: Only variable and named common block can be in BIND statement
bind(c) :: sub
!PORTABILITY: Global name 'm' conflicts with a module
!PORTABILITY: Name 'm' declared in a module should not have the same name as the module
bind(c) :: m ! no error for implicit type variable
type my_type
integer :: i
end type
!ERROR: Only variable and named common block can be in BIND statement
bind(c) :: my_type
enum, bind(c) ! no error
enumerator :: SUNDAY, MONDAY
end enum
integer :: x, y, z = 1
common /blk/ y
bind(c) :: x, /blk/, z ! no error for variable and common block
bind(c) :: implicit_i ! no error for implicit type variable
!ERROR: 'implicit_blk' appears as a COMMON block in a BIND statement but not in a COMMON statement
bind(c) :: /implicit_blk/
contains
subroutine sub() bind(c)
end
end