squiid/llvm
1
0
Fork 0
Code Issues Pull requests Activity
llvm/flang/test/semantics/CMakeLists.txt

94 lines
2.2 KiB
CMake
Raw Normal View History

[flang] Add name resolution tests The Fortran source files in test/semantics all contain expected errors in comments. The script test_errors.sh compiles a file with 'f18 -fdebug-resolve-names -fparse-only' and compares the actual errors produced against the expected ones. The change to resolve15.f90 is necessary because test_errors.sh can't handle two expected errors for the same source line. A useful command to run these is 'ctest -R f90 --output-on-failure'. -R means only run tests with f90 in the name --output-on-failure prints the output of test_errors.sh when a test fails, showing the expected and actual messages that differ. Original-commit: flang-compiler/f18@df18ee7bc95628503b37648d98c5ae25bc74b227 Reviewed-on: https://github.com/flang-compiler/f18/pull/105
2018-06-15 23:54:34 +02:00
# Copyright (c) 2018, NVIDIA CORPORATION. All rights reserved.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# Run tests with test_errors.sh. It compiles the test with f18 and compares
# actual errors produced with expected ones listed in the source.
[flang] Support intent-stmt and resolve subprogram prefixes and suffixes. Recognize `IntentStmt` and use `HandleAttributeStmt()` to implement it as is done with other attribute statements. Add `Attr::INTENT_INOUT` as a separate attribute for `INTENT(INOUT)`. Collect attributes from the prefix and suffix of `FunctionStmt` and `SubroutineStmt` (including `BIND(C)`) and set them on the subprogram symbol. Create a test for this using `test_symbol.sh`. It compiles with `-funparse-with-symbols` and compares the output with the symbols in comments in the input. Change `test_errors.sh` to be similar to `test_symbol.sh`: check usage and allow `F18` environment variable to override the path to the compiler. Original-commit: flang-compiler/f18@384828a22f53d828a3140640ca89f5819ada394d Reviewed-on: https://github.com/flang-compiler/f18/pull/120 Tree-same-pre-rewrite: false
2018-07-12 02:45:13 +02:00
# These test files have expected errors in the source
set(ERROR_TESTS
[flang] Add name resolution tests The Fortran source files in test/semantics all contain expected errors in comments. The script test_errors.sh compiles a file with 'f18 -fdebug-resolve-names -fparse-only' and compares the actual errors produced against the expected ones. The change to resolve15.f90 is necessary because test_errors.sh can't handle two expected errors for the same source line. A useful command to run these is 'ctest -R f90 --output-on-failure'. -R means only run tests with f90 in the name --output-on-failure prints the output of test_errors.sh when a test fails, showing the expected and actual messages that differ. Original-commit: flang-compiler/f18@df18ee7bc95628503b37648d98c5ae25bc74b227 Reviewed-on: https://github.com/flang-compiler/f18/pull/105
2018-06-15 23:54:34 +02:00
implicit01.f90
implicit02.f90
implicit03.f90
implicit04.f90
implicit05.f90
implicit06.f90
implicit07.f90
[flang] Add support for BLOCK construct A `BLOCK` statement opens a new scope. It is different from other scopes in that implicitly typed entities are defined in the enclosing non-block scope, not immediately in the block. This means that `IMPORT` statements can cause them to be hidden. Check that blocks can't have `IMPLICIT` statements in them. It is simpler for the parser not to deal with the different between a specification-part and a block-specification-part. Change `ImplicitRules` to have a parent that is consulted when there isn't an answer in the current one. For an interface body that does not happen but for all other nested scopes it does. This parent link eliminates the need for the `implicitRules_` stack. Make `isImplicitNoneType_` and `isImplicitNoneExternal_` optional: not set means look in parent. Fixes flang-compiler/f18#71. Remove `CurrNonTypeScope()` and put the logic in `Symbol::FindSymbol`. Original-commit: flang-compiler/f18@a153a2ee33ff493df6d4fb5e20d99d302d76ab43 Reviewed-on: https://github.com/flang-compiler/f18/pull/169 Tree-same-pre-rewrite: false
2018-08-27 20:48:49 +02:00
implicit08.f90
[flang] Add name resolution tests The Fortran source files in test/semantics all contain expected errors in comments. The script test_errors.sh compiles a file with 'f18 -fdebug-resolve-names -fparse-only' and compares the actual errors produced against the expected ones. The change to resolve15.f90 is necessary because test_errors.sh can't handle two expected errors for the same source line. A useful command to run these is 'ctest -R f90 --output-on-failure'. -R means only run tests with f90 in the name --output-on-failure prints the output of test_errors.sh when a test fails, showing the expected and actual messages that differ. Original-commit: flang-compiler/f18@df18ee7bc95628503b37648d98c5ae25bc74b227 Reviewed-on: https://github.com/flang-compiler/f18/pull/105
2018-06-15 23:54:34 +02:00
resolve01.f90
resolve02.f90
resolve03.f90
resolve04.f90
resolve05.f90
resolve06.f90
resolve07.f90
resolve08.f90
resolve09.f90
resolve10.f90
resolve11.f90
resolve12.f90
resolve13.f90
resolve14.f90
resolve15.f90
resolve16.f90
resolve17.f90
resolve18.f90
resolve19.f90
resolve20.f90
[flang] Name resolution for derived types. This consists of: - a new kind of symbols to represent them with DerivedTypeDetails - creating symbols for derived types when they are declared - creating a new kind of scope for the type to hold component symbols - resolving entity declarations of objects of derived type - resolving references to objects of derived type and to components - handling derived types with same name as generic Type parameters are not yet implemented. Refactor DeclTypeSpec to be a value class wrapping an IntrinsicTypeSpec or a DerivedTypeSpec (or neither in the TypeStar and ClassStar cases). Store DerivedTypeSpec objects in a new structure the current scope MakeDerivedTypeSpec so that DeclTypeSpec can just contain a pointer to them, as it currently does for intrinsic types. In GenericDetails, add derivedType field to handle case where generic and derived type have the same name. The generic is in the scope and the derived type is referenced from the generic, similar to the case where a generic and specific have the same name. When one of these names is mis-recognized, we sometimes have to fix up the 'occurrences' lists of the symbols. Assign implicit types as soon as an entity is encountered that requires one. Otherwise implicit derived types won't work. When we see 'x%y' we have to know the type of x in order to resolve y. Add an Implicit flag to mark symbols that were implicitly typed For symbols that introduce a new scope, include a pointer back to that scope. Add CurrNonTypeScope() for the times when we want the current scope but ignoring derived type scopes. For example, that happens when looking for types or parameters, or creating implicit symbols. Original-commit: flang-compiler/f18@9bd16da020b64b78ed3928e0244765cd2e2d8068 Reviewed-on: https://github.com/flang-compiler/f18/pull/109
2018-06-22 17:21:19 +02:00
resolve21.f90
resolve22.f90
resolve23.f90
[flang] Check consistency of generic interfaces. The specific procedures in a generic interface must be all functions or all subroutines. If there is a derived type with the same name they can only be functions. Original-commit: flang-compiler/f18@e02cef047a02585caba550da01dcf7f5e75942dd Reviewed-on: https://github.com/flang-compiler/f18/pull/114 Tree-same-pre-rewrite: false
2018-07-05 19:28:34 +02:00
resolve24.f90
[flang] Correctly resolve generics with forward references When a procedure is included by name in a generic (either with a procedure statement in a generic interface or with a generic statement) we can't immediately resolve it to a subprogram symbol. That is because the subprogram may be defined later in the specification part. Instead, collect the names (and whether they should be module procedures) and resolve them to symbols at the end of the specification part. Also detect duplicate names then. This is needed for module file reading as these forward references can occur there. Write generics to module file using generic statements. This allows us to include the access-spec. Original-commit: flang-compiler/f18@d11d002084af4a25d0c9a63dbe6460530b56adc7 Reviewed-on: https://github.com/flang-compiler/f18/pull/132
2018-07-20 19:46:11 +02:00
resolve25.f90
[flang] Add support for submodules Symbols for submodules have `ModuleDetails` with `isSubmodule` set. Scopes for submodules have `Module` kind and have a parent scope that is also `Module` kind. Scopes for modules now contain a mapping of submodule name to scope so that we can find them without having to search the scope tree or re-read their `.mod` file. The module file for submodule `s` with ancestor module `m` is named `m-s.mod`. The tree structure of scopes means module file writing is now recursive. Similarly, reading the module file for a submodule may require reading the module files of its parent and ancestor. `ResolveNames` now requires the parent scope to be passed in -- it is not always the global scope. `test_modfiles.sh` now handles an argument that is a filename glob so that the test can involve multiple files. This allows `modfile09` to test reading of `.mod` files for modules and submodules. Original-commit: flang-compiler/f18@2e4424dbc8cc5803d561274dbf70005afe7e65dc Reviewed-on: https://github.com/flang-compiler/f18/pull/160 Tree-same-pre-rewrite: false
2018-08-03 01:21:27 +02:00
resolve26.f90
resolve27.f90
[flang] Implement host association and import statements Host association is done by search for symbols using `Scope::FindSymbol()` which looks for the the name in the parent scope if the import rules permit it. Import statements are implemented using `importKind_` and `importNames_` in class `Scope`. Most of the constraints are checked when the `ImportStmt` is encountered. `CheckImports()` is called at the end of the `SpecificationPart` to verify the names mentioned in the IMPORT statement. That has to happen then so that we can detect if an imported name is hidden by a declaration in the current scope. Original-commit: flang-compiler/f18@0d50c8a8ba12692e6246c4e1a8a098f2850aba3a Reviewed-on: https://github.com/flang-compiler/f18/pull/167 Tree-same-pre-rewrite: false
2018-08-23 01:05:06 +02:00
resolve28.f90
resolve29.f90
[flang] Add support for BLOCK construct A `BLOCK` statement opens a new scope. It is different from other scopes in that implicitly typed entities are defined in the enclosing non-block scope, not immediately in the block. This means that `IMPORT` statements can cause them to be hidden. Check that blocks can't have `IMPLICIT` statements in them. It is simpler for the parser not to deal with the different between a specification-part and a block-specification-part. Change `ImplicitRules` to have a parent that is consulted when there isn't an answer in the current one. For an interface body that does not happen but for all other nested scopes it does. This parent link eliminates the need for the `implicitRules_` stack. Make `isImplicitNoneType_` and `isImplicitNoneExternal_` optional: not set means look in parent. Fixes flang-compiler/f18#71. Remove `CurrNonTypeScope()` and put the logic in `Symbol::FindSymbol`. Original-commit: flang-compiler/f18@a153a2ee33ff493df6d4fb5e20d99d302d76ab43 Reviewed-on: https://github.com/flang-compiler/f18/pull/169 Tree-same-pre-rewrite: false
2018-08-27 20:48:49 +02:00
resolve30.f90
[flang] Small improvements to name resolution Resolve names and do implicit typing in ArrayElement and LoopBounds. Fix problem with creation of UseErrorDetails: when a conflict occurs, record both the original USE and the new one. Resolve the type name in TypeAttrSpec::Extends. Move CheckUseError to DeclarationVisitor so that it can be used in ResolveDerivedType. Report error on unresolved names. I.e. after name resolution, check each parser::Name and verify we have a Symbol for it. This is on by default now but it could be an option. Original-commit: flang-compiler/f18@1c8cbc6e53cc7e1b6909bbedf5370e27fd11572f Reviewed-on: https://github.com/flang-compiler/f18/pull/173 Tree-same-pre-rewrite: false
2018-08-29 20:38:12 +02:00
resolve31.f90
[flang] Add name resolution tests The Fortran source files in test/semantics all contain expected errors in comments. The script test_errors.sh compiles a file with 'f18 -fdebug-resolve-names -fparse-only' and compares the actual errors produced against the expected ones. The change to resolve15.f90 is necessary because test_errors.sh can't handle two expected errors for the same source line. A useful command to run these is 'ctest -R f90 --output-on-failure'. -R means only run tests with f90 in the name --output-on-failure prints the output of test_errors.sh when a test fails, showing the expected and actual messages that differ. Original-commit: flang-compiler/f18@df18ee7bc95628503b37648d98c5ae25bc74b227 Reviewed-on: https://github.com/flang-compiler/f18/pull/105
2018-06-15 23:54:34 +02:00
)
[flang] Support intent-stmt and resolve subprogram prefixes and suffixes. Recognize `IntentStmt` and use `HandleAttributeStmt()` to implement it as is done with other attribute statements. Add `Attr::INTENT_INOUT` as a separate attribute for `INTENT(INOUT)`. Collect attributes from the prefix and suffix of `FunctionStmt` and `SubroutineStmt` (including `BIND(C)`) and set them on the subprogram symbol. Create a test for this using `test_symbol.sh`. It compiles with `-funparse-with-symbols` and compares the output with the symbols in comments in the input. Change `test_errors.sh` to be similar to `test_symbol.sh`: check usage and allow `F18` environment variable to override the path to the compiler. Original-commit: flang-compiler/f18@384828a22f53d828a3140640ca89f5819ada394d Reviewed-on: https://github.com/flang-compiler/f18/pull/120 Tree-same-pre-rewrite: false
2018-07-12 02:45:13 +02:00
# These test files have expected symbols in the source
set(SYMBOL_TESTS
symbol01.f90
[flang] Implement host association and import statements Host association is done by search for symbols using `Scope::FindSymbol()` which looks for the the name in the parent scope if the import rules permit it. Import statements are implemented using `importKind_` and `importNames_` in class `Scope`. Most of the constraints are checked when the `ImportStmt` is encountered. `CheckImports()` is called at the end of the `SpecificationPart` to verify the names mentioned in the IMPORT statement. That has to happen then so that we can detect if an imported name is hidden by a declaration in the current scope. Original-commit: flang-compiler/f18@0d50c8a8ba12692e6246c4e1a8a098f2850aba3a Reviewed-on: https://github.com/flang-compiler/f18/pull/167 Tree-same-pre-rewrite: false
2018-08-23 01:05:06 +02:00
symbol02.f90
symbol03.f90
[flang] Add another host-associate test Verify that a derived type component does not hide a type of the same name in its host. Original-commit: flang-compiler/f18@212d84cb2f555ae77fae6b5724266ea894250bd1 Reviewed-on: https://github.com/flang-compiler/f18/pull/167 Tree-same-pre-rewrite: false
2018-08-23 16:41:06 +02:00
symbol04.f90
[flang] Add support for BLOCK construct A `BLOCK` statement opens a new scope. It is different from other scopes in that implicitly typed entities are defined in the enclosing non-block scope, not immediately in the block. This means that `IMPORT` statements can cause them to be hidden. Check that blocks can't have `IMPLICIT` statements in them. It is simpler for the parser not to deal with the different between a specification-part and a block-specification-part. Change `ImplicitRules` to have a parent that is consulted when there isn't an answer in the current one. For an interface body that does not happen but for all other nested scopes it does. This parent link eliminates the need for the `implicitRules_` stack. Make `isImplicitNoneType_` and `isImplicitNoneExternal_` optional: not set means look in parent. Fixes flang-compiler/f18#71. Remove `CurrNonTypeScope()` and put the logic in `Symbol::FindSymbol`. Original-commit: flang-compiler/f18@a153a2ee33ff493df6d4fb5e20d99d302d76ab43 Reviewed-on: https://github.com/flang-compiler/f18/pull/169 Tree-same-pre-rewrite: false
2018-08-27 20:48:49 +02:00
symbol05.f90
[flang] Support intent-stmt and resolve subprogram prefixes and suffixes. Recognize `IntentStmt` and use `HandleAttributeStmt()` to implement it as is done with other attribute statements. Add `Attr::INTENT_INOUT` as a separate attribute for `INTENT(INOUT)`. Collect attributes from the prefix and suffix of `FunctionStmt` and `SubroutineStmt` (including `BIND(C)`) and set them on the subprogram symbol. Create a test for this using `test_symbol.sh`. It compiles with `-funparse-with-symbols` and compares the output with the symbols in comments in the input. Change `test_errors.sh` to be similar to `test_symbol.sh`: check usage and allow `F18` environment variable to override the path to the compiler. Original-commit: flang-compiler/f18@384828a22f53d828a3140640ca89f5819ada394d Reviewed-on: https://github.com/flang-compiler/f18/pull/120 Tree-same-pre-rewrite: false
2018-07-12 02:45:13 +02:00
)
[flang] Add tests for .mod file writing The source files contain the expected contents of generated .mod files. `test_modfile.sh` compiles the source file and verifies that the correct .mod files are generated. Original-commit: flang-compiler/f18@a23f53c1a7d6f1dba157c1bc87ebc046d3b818e6 Reviewed-on: https://github.com/flang-compiler/f18/pull/126 Tree-same-pre-rewrite: false
2018-07-17 01:24:14 +02:00
# These test files have expected .mod file contents in the source
set(MODFILE_TESTS
modfile01.f90
modfile02.f90
modfile03.f90
[flang] Add a .mod file test with subprograms The .mod file just contains the API. Test that prefixes and suffixes on the declaration get correctly persisted. Original-commit: flang-compiler/f18@eb2a6deb4fe12bae83fc3cb2366d056cf50cc9a5 Reviewed-on: https://github.com/flang-compiler/f18/pull/126 Tree-same-pre-rewrite: false
2018-07-17 01:44:07 +02:00
modfile04.f90
[flang] Handle VOLATILE or ASYNCHRONOUS added to use-associated entity When a symbol is use-associated, the VOLATILE and ASYNCHRONOUS attributes can be added. When that happens it must be recorded in the .mod file. Original-commit: flang-compiler/f18@44fa9e5ba4172f75abe4194e7f58b26a99646cdc Reviewed-on: https://github.com/flang-compiler/f18/pull/126
2018-07-17 15:39:38 +02:00
modfile05.f90
[flang] Support writing interfaces in module files. Write symbols for external subprogram interfaces as interface-stmts. Those go in the decls part of the module file, as opposed to contained subprograms which go in the contains part. See modfile06.f90. Write symbols with GenericDetails to module files. The specific procedures of a generic interface are always written as procedure-stmts. If they also have specific interfaces those are written in a separate interface-stmt. See modfile07.f90. Fix a bug where `real, external :: f` was not written like `real f; external f`. We have to notice the EXTERNAL attribute on the type-declaration-stmt and convert the entity to a procedure entity. See modfile08.f90. Fix a bug where a use-associated symbol is referenced in a procedure-designator. We were not resolving that correctly. Change ModFileWriter::PutEntity to include the kind of Details when it reports an internal error due to a kind it can't handle. Make DetailsToString public to support that. Change test_errors.sh to fail if the f18 command exits due to a signal. We were missing bugs where the correct errors were written out but then module file writing crashed (due to failure to handle generics mentioned above). Non-zero exit status is okay because we are expecting compilation errors. Change test_modfile.sh to allow for the expected module file contents to be indented so the tests are easier to read. Original-commit: flang-compiler/f18@82a7931e51c63ba21f17261727e1e9dc4167dcc9 Reviewed-on: https://github.com/flang-compiler/f18/pull/132 Tree-same-pre-rewrite: false
2018-07-19 22:28:24 +02:00
modfile06.f90
modfile07.f90
modfile08.f90
[flang] Add support for submodules Symbols for submodules have `ModuleDetails` with `isSubmodule` set. Scopes for submodules have `Module` kind and have a parent scope that is also `Module` kind. Scopes for modules now contain a mapping of submodule name to scope so that we can find them without having to search the scope tree or re-read their `.mod` file. The module file for submodule `s` with ancestor module `m` is named `m-s.mod`. The tree structure of scopes means module file writing is now recursive. Similarly, reading the module file for a submodule may require reading the module files of its parent and ancestor. `ResolveNames` now requires the parent scope to be passed in -- it is not always the global scope. `test_modfiles.sh` now handles an argument that is a filename glob so that the test can involve multiple files. This allows `modfile09` to test reading of `.mod` files for modules and submodules. Original-commit: flang-compiler/f18@2e4424dbc8cc5803d561274dbf70005afe7e65dc Reviewed-on: https://github.com/flang-compiler/f18/pull/160 Tree-same-pre-rewrite: false
2018-08-03 01:21:27 +02:00
modfile09-*.f90
[flang] Add tests for .mod file writing The source files contain the expected contents of generated .mod files. `test_modfile.sh` compiles the source file and verifies that the correct .mod files are generated. Original-commit: flang-compiler/f18@a23f53c1a7d6f1dba157c1bc87ebc046d3b818e6 Reviewed-on: https://github.com/flang-compiler/f18/pull/126 Tree-same-pre-rewrite: false
2018-07-17 01:24:14 +02:00
)
[flang] Support intent-stmt and resolve subprogram prefixes and suffixes. Recognize `IntentStmt` and use `HandleAttributeStmt()` to implement it as is done with other attribute statements. Add `Attr::INTENT_INOUT` as a separate attribute for `INTENT(INOUT)`. Collect attributes from the prefix and suffix of `FunctionStmt` and `SubroutineStmt` (including `BIND(C)`) and set them on the subprogram symbol. Create a test for this using `test_symbol.sh`. It compiles with `-funparse-with-symbols` and compares the output with the symbols in comments in the input. Change `test_errors.sh` to be similar to `test_symbol.sh`: check usage and allow `F18` environment variable to override the path to the compiler. Original-commit: flang-compiler/f18@384828a22f53d828a3140640ca89f5819ada394d Reviewed-on: https://github.com/flang-compiler/f18/pull/120 Tree-same-pre-rewrite: false
2018-07-12 02:45:13 +02:00
foreach(test ${ERROR_TESTS})
[flang] Add name resolution tests The Fortran source files in test/semantics all contain expected errors in comments. The script test_errors.sh compiles a file with 'f18 -fdebug-resolve-names -fparse-only' and compares the actual errors produced against the expected ones. The change to resolve15.f90 is necessary because test_errors.sh can't handle two expected errors for the same source line. A useful command to run these is 'ctest -R f90 --output-on-failure'. -R means only run tests with f90 in the name --output-on-failure prints the output of test_errors.sh when a test fails, showing the expected and actual messages that differ. Original-commit: flang-compiler/f18@df18ee7bc95628503b37648d98c5ae25bc74b227 Reviewed-on: https://github.com/flang-compiler/f18/pull/105
2018-06-15 23:54:34 +02:00
add_test(NAME ${test} COMMAND ${CMAKE_CURRENT_SOURCE_DIR}/test_errors.sh ${test})
endforeach()
[flang] Support intent-stmt and resolve subprogram prefixes and suffixes. Recognize `IntentStmt` and use `HandleAttributeStmt()` to implement it as is done with other attribute statements. Add `Attr::INTENT_INOUT` as a separate attribute for `INTENT(INOUT)`. Collect attributes from the prefix and suffix of `FunctionStmt` and `SubroutineStmt` (including `BIND(C)`) and set them on the subprogram symbol. Create a test for this using `test_symbol.sh`. It compiles with `-funparse-with-symbols` and compares the output with the symbols in comments in the input. Change `test_errors.sh` to be similar to `test_symbol.sh`: check usage and allow `F18` environment variable to override the path to the compiler. Original-commit: flang-compiler/f18@384828a22f53d828a3140640ca89f5819ada394d Reviewed-on: https://github.com/flang-compiler/f18/pull/120 Tree-same-pre-rewrite: false
2018-07-12 02:45:13 +02:00
foreach(test ${SYMBOL_TESTS})
add_test(NAME ${test} COMMAND ${CMAKE_CURRENT_SOURCE_DIR}/test_symbols.sh ${test})
endforeach()
[flang] Add tests for .mod file writing The source files contain the expected contents of generated .mod files. `test_modfile.sh` compiles the source file and verifies that the correct .mod files are generated. Original-commit: flang-compiler/f18@a23f53c1a7d6f1dba157c1bc87ebc046d3b818e6 Reviewed-on: https://github.com/flang-compiler/f18/pull/126 Tree-same-pre-rewrite: false
2018-07-17 01:24:14 +02:00
foreach(test ${MODFILE_TESTS})
add_test(NAME ${test} COMMAND ${CMAKE_CURRENT_SOURCE_DIR}/test_modfile.sh ${test})
endforeach()
Reference in a new issue Copy permalink