maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/flang/test/Semantics/data02.f90

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

33 lines
791 B
Fortran
Raw Normal View History

[flang] Update the regression tests to use the new driver when enabled This patch updates most of the remaining regression tests (~400) to use `flang-new` rather then `f18` when `FLANG_BUILD_NEW_DRIVER` is set. This allows us to share more Flang regression tests between `f18` and `flang-new`. A handful of tests have not been ported yet - these are currently either failing or not supported by the new driver. Summary of changes: * RUN lines in tests are updated to use `%flang_fc1` instead of `%f18` * option spellings in tests are updated to forms accepted by both `f18` and `flang-new` * variables in Bash scripts are renamed (e.g. F18 --> FLANG_FC1) The updated tests will now be run with the new driver, `flang-new`, whenever it is enabled (i.e when `FLANG_BUILD_NEW_DRIVER` is set). Although this patch touches many files, vast majority of the changes are automatic: ``` grep -IEZlr "%f18" flang/test/ | xargs -0 -l sed -i 's/%f18/%flang_fc1/g ``` Differential Revision: https://reviews.llvm.org/D100309
2021-04-12 20:27:49 +08:00
! RUN: %S/test_errors.sh %s %t %flang_fc1
[flang] Expression analysis on DataStmtConstant Data statements contains expressions but they are not wrapped in one of the kinds of parse tree nodes that are analyzed, like `parser::Expr`. So potential errors were not discovered. Change `ExprChecker` to handle `DataStmtConstant` and analyze any expressions that are contained in it. Note that the analyzed form of the expression is not yet saved in the parse tree. Original-commit: flang-compiler/f18@8bdaf0a521f6630ec2c369b2c41484eff4803d6e Reviewed-on: https://github.com/flang-compiler/f18/pull/1044
2020-03-02 23:59:29 +08:00
! Check that expressions are analyzed in data statements
subroutine s1
type :: t
character(1) :: c
end type
type(t) :: x
[flang] Support known constant lengths in DynamicType The constexpr-capable class evaluate::DynamicType represented CHARACTER length only with a nullable pointer into the declared parameters of types in the symbol table, which works fine for anything with a declaration but turns out to not suffice to describe the results of the ACHAR() and CHAR() intrinsic functions. So extend DynamicType to also accommodate known constant CHARACTER lengths, too; use them for ACHAR & CHAR; clean up several use sites and fix regressions found in test. Differential Revision: https://reviews.llvm.org/D103571
2021-06-03 08:13:55 +08:00
!ERROR: Value in structure constructor of type INTEGER(4) is incompatible with component 'c' of type CHARACTER(KIND=1,LEN=1_8)
[flang] Expression analysis on DataStmtConstant Data statements contains expressions but they are not wrapped in one of the kinds of parse tree nodes that are analyzed, like `parser::Expr`. So potential errors were not discovered. Change `ExprChecker` to handle `DataStmtConstant` and analyze any expressions that are contained in it. Note that the analyzed form of the expression is not yet saved in the parse tree. Original-commit: flang-compiler/f18@8bdaf0a521f6630ec2c369b2c41484eff4803d6e Reviewed-on: https://github.com/flang-compiler/f18/pull/1044
2020-03-02 23:59:29 +08:00
data x /t(1)/
end
subroutine s2
real :: x1, x2
integer :: i1, i2
!ERROR: Unsupported REAL(KIND=99)
data x1 /1.0_99/
!ERROR: Unsupported REAL(KIND=99)
data x2 /-1.0_99/
!ERROR: INTEGER(KIND=99) is not a supported type
data i1 /1_99/
!ERROR: INTEGER(KIND=99) is not a supported type
data i2 /-1_99/
end
subroutine s3
complex :: z1, z2
!ERROR: Unsupported REAL(KIND=99)
data z1 /(1.0, 2.0_99)/
!ERROR: Unsupported REAL(KIND=99)
data z2 /-(1.0, 2.0_99)/
end