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/symbol16.f90

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

28 lines
598 B
Fortran
Raw Normal View History

[flang][NFC] Simplify semantics test scripts There were several different ways of handling the option to f18 to find predefined modules: - test_errors.sh was created by cmake substituting FLANG_INTRINSIC_MODULES_DIR into test_errors.sh.in - some tests used the flang script which has the option built it - some tests used %f18_with_includes which was replaced by the path to f18 plus the -I option - some included -I../../include/flang in their run command To make this more consistent, change %f18 to include the -intrinsic-module-directory option and use it everywhere, including to replace %flang and %f18_with_includes. This requires changing all of the invocations of the test scripts to put %f18 at the end so that it can expand to more than one argument. This eliminates the need to generate test_errors.sh which means we don't need flang/test/Semantics/CMakeLists.txt or the %B substitution. That makes the test_errors.sh command like the others, replacing %B/test/Semantics/test_errors.sh with %S/test_errors.sh. Also remove the OPTIONS: functionality as custom options can be included in the RUN: command. And remove -I/../../include/flang as that is now always included. Differential Revision: https://reviews.llvm.org/D79634
2020-05-12 02:38:53 +08:00
! RUN: %S/test_symbols.sh %s %t %f18
[flang] Fix bug with statement functions When the name of a statement function was previously declared, we weren't correctly recognizing it as a statement function. E.g. ``` integer :: f, i f(i) = i + 1 ``` `f` was entered in the symbol table with `EntityDetails` and the `parser::Name` on the first line was resolved to that symbol. On the second line we replaced the symbol for `f` in the scope with a subprogram symbol, but that didn't change the symbol in the first `parser::Name`. The fix requires: 1. don't erase the original symbol for `f`, just replace its details 2. when we erase the symbol for `f` in the subprogram scope, don't unresolve it Original-commit: flang-compiler/f18@31212686ea357503840c0562853c6977bfc1ffe5
2019-08-27 06:46:49 +08:00
! Statement functions
!DEF: /p1 MainProgram
program p1
[flang] Fix implicit declarations in statement functions If a symbol (that is not a dummy argument) is implicitly declared inside a statement function, don't create it in the statement function's scope. Instead, treat statement functions like blocks when finding the inclusive scope and create the symbol there. Add a new flag, StmtFunction, to symbols that represent statement functions. Differential Revision: https://reviews.llvm.org/D84588
2020-07-27 03:13:36 +08:00
!DEF: /p1/f (Function, StmtFunction) Subprogram INTEGER(4)
[flang] Fix bug with statement functions When the name of a statement function was previously declared, we weren't correctly recognizing it as a statement function. E.g. ``` integer :: f, i f(i) = i + 1 ``` `f` was entered in the symbol table with `EntityDetails` and the `parser::Name` on the first line was resolved to that symbol. On the second line we replaced the symbol for `f` in the scope with a subprogram symbol, but that didn't change the symbol in the first `parser::Name`. The fix requires: 1. don't erase the original symbol for `f`, just replace its details 2. when we erase the symbol for `f` in the subprogram scope, don't unresolve it Original-commit: flang-compiler/f18@31212686ea357503840c0562853c6977bfc1ffe5
2019-08-27 06:46:49 +08:00
!DEF: /p1/i ObjectEntity INTEGER(4)
!DEF: /p1/j ObjectEntity INTEGER(4)
integer f, i, j
!REF: /p1/f
!REF: /p1/i
!DEF: /p1/f/i ObjectEntity INTEGER(4)
f(i) = i + 1
!REF: /p1/j
!REF: /p1/f
j = f(2)
end program
[flang] Fix implicit declarations in statement functions If a symbol (that is not a dummy argument) is implicitly declared inside a statement function, don't create it in the statement function's scope. Instead, treat statement functions like blocks when finding the inclusive scope and create the symbol there. Add a new flag, StmtFunction, to symbols that represent statement functions. Differential Revision: https://reviews.llvm.org/D84588
2020-07-27 03:13:36 +08:00
!DEF: /p2 MainProgram
program p2
!DEF: /p2/f (Function, StmtFunction) Subprogram REAL(4)
!DEF: /p2/f/x (Implicit) ObjectEntity REAL(4)
!DEF: /p2/y (Implicit) ObjectEntity REAL(4)
f(x) = y
!REF: /p2/y
y = 1.0
end program