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.
17 lines
798 B
Fortran
17 lines
798 B
Fortran
! RUN: %python %S/test_errors.py %s %flang_fc1 -Werror -pedantic
|
|
!PORTABILITY: nonstandard usage: generalized COMPLEX constructor
|
|
!PORTABILITY: Real part of complex constructor is not scalar
|
|
complex, parameter :: z1(*) = ([1.,2.], 3.)
|
|
!PORTABILITY: nonstandard usage: generalized COMPLEX constructor
|
|
!PORTABILITY: Imaginary part of complex constructor is not scalar
|
|
complex, parameter :: z2(*) = (4., [5.,6.])
|
|
real, parameter :: aa(*) = [7.,8.]
|
|
!PORTABILITY: Real part of complex literal constant is not scalar
|
|
complex, parameter :: z3(*) = (aa, 9.)
|
|
!PORTABILITY: Imaginary part of complex literal constant is not scalar
|
|
complex, parameter :: z4(*) = (10., aa)
|
|
!We need a nonzero exit status to make test_errors.py look at messages :-(
|
|
!WARNING: division by zero
|
|
real, parameter :: xxx = 1./0.
|
|
end
|