maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/flang/test/Frontend/input-output-file.f90

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

35 lines
1.2 KiB
Fortran
Raw Normal View History

[Flang][Driver] Add infrastructure for basic frontend actions and file I/O This patch introduces the dependencies required to read and manage input files provided by the command line option. It also adds the infrastructure to create and write to output files. The output is sent to either stdout or a file (specified with the `-o` flag). Separately, in order to be able to test the code for file I/O, it adds infrastructure to create frontend actions. As a basic testable example, it adds the `InputOutputTest` FrontendAction. The sole purpose of this action is to read a file from the command line and print it either to stdout or the output file. This action is run by using the `-test-io` flag also introduced in this patch (available for `flang-new` and `flang-new -fc1`). With this patch: ``` flang-new -test-io input-file.f90 ``` will read input-file.f90 and print it in the output file. The `InputOutputTest` frontend action has been introduced primarily to facilitate testing. It is hidden from users (i.e. it's only displayed with `--help-hidden`). Currently Clang doesn’t have an equivalent action. `-test-io` is used to trigger the InputOutputTest action in the Flang frontend driver. This patch makes sure that “flang-new” forwards it to “flang-new -fc1" by creating a preprocessor job. However, in Flang.cpp, `-test-io` is passed to “flang-new -fc1” without `-E`. This way we make sure that the preprocessor is _not_ run in the frontend driver. This is the desired behaviour: `-test-io` should only read the input file and print it to the output stream. co-authored-by: Andrzej Warzynski <andrzej.warzynski@arm.com> Differential Revision: https://reviews.llvm.org/D87989
2020-10-24 19:33:19 +08:00
! RUN: rm -rf %S/input-output-file.txt
! REQUIRES: new-flang-driver
!--------------------------
! FLANG DRIVER (flang-new)
!--------------------------
! TEST 1: Print to stdout (implicit)
[flang][driver] Use --match-full-lines in tests for `-test-io` Use `--match-full-lines` to make sure that FileCheck doesn't match the output against the `CHECK` lines (which, like other comments, are also printed). More specifically, we want to make sure that the following `check` in the input file: ``` ! CHECK: <some-fortran-input> ``` is matched by FileCheck with `<some-fortran-input>` in the generated output. Without `--match-full-lines`, that check-line will be matched with `!CHECK: <some-fortran-input>` instead (which is also printed together with other contents of the file). Adding `--match-full-lines` makes the tests stricter and this change revealed that some `check`s were passing only because that flag was missing. These are updated accordingly. Reviewed By: CarolineConcatto, sameeranjoshi Differential Revision: https://reviews.llvm.org/D90306
2020-11-02 17:34:27 +08:00
! RUN: %flang-new -test-io %s 2>&1 | FileCheck %s --match-full-lines
[Flang][Driver] Add infrastructure for basic frontend actions and file I/O This patch introduces the dependencies required to read and manage input files provided by the command line option. It also adds the infrastructure to create and write to output files. The output is sent to either stdout or a file (specified with the `-o` flag). Separately, in order to be able to test the code for file I/O, it adds infrastructure to create frontend actions. As a basic testable example, it adds the `InputOutputTest` FrontendAction. The sole purpose of this action is to read a file from the command line and print it either to stdout or the output file. This action is run by using the `-test-io` flag also introduced in this patch (available for `flang-new` and `flang-new -fc1`). With this patch: ``` flang-new -test-io input-file.f90 ``` will read input-file.f90 and print it in the output file. The `InputOutputTest` frontend action has been introduced primarily to facilitate testing. It is hidden from users (i.e. it's only displayed with `--help-hidden`). Currently Clang doesn’t have an equivalent action. `-test-io` is used to trigger the InputOutputTest action in the Flang frontend driver. This patch makes sure that “flang-new” forwards it to “flang-new -fc1" by creating a preprocessor job. However, in Flang.cpp, `-test-io` is passed to “flang-new -fc1” without `-E`. This way we make sure that the preprocessor is _not_ run in the frontend driver. This is the desired behaviour: `-test-io` should only read the input file and print it to the output stream. co-authored-by: Andrzej Warzynski <andrzej.warzynski@arm.com> Differential Revision: https://reviews.llvm.org/D87989
2020-10-24 19:33:19 +08:00
! TEST 2: Print to stdout (explicit)
[flang][driver] Use --match-full-lines in tests for `-test-io` Use `--match-full-lines` to make sure that FileCheck doesn't match the output against the `CHECK` lines (which, like other comments, are also printed). More specifically, we want to make sure that the following `check` in the input file: ``` ! CHECK: <some-fortran-input> ``` is matched by FileCheck with `<some-fortran-input>` in the generated output. Without `--match-full-lines`, that check-line will be matched with `!CHECK: <some-fortran-input>` instead (which is also printed together with other contents of the file). Adding `--match-full-lines` makes the tests stricter and this change revealed that some `check`s were passing only because that flag was missing. These are updated accordingly. Reviewed By: CarolineConcatto, sameeranjoshi Differential Revision: https://reviews.llvm.org/D90306
2020-11-02 17:34:27 +08:00
! RUN: %flang-new -test-io -o - %s 2>&1 | FileCheck %s --match-full-lines
[Flang][Driver] Add infrastructure for basic frontend actions and file I/O This patch introduces the dependencies required to read and manage input files provided by the command line option. It also adds the infrastructure to create and write to output files. The output is sent to either stdout or a file (specified with the `-o` flag). Separately, in order to be able to test the code for file I/O, it adds infrastructure to create frontend actions. As a basic testable example, it adds the `InputOutputTest` FrontendAction. The sole purpose of this action is to read a file from the command line and print it either to stdout or the output file. This action is run by using the `-test-io` flag also introduced in this patch (available for `flang-new` and `flang-new -fc1`). With this patch: ``` flang-new -test-io input-file.f90 ``` will read input-file.f90 and print it in the output file. The `InputOutputTest` frontend action has been introduced primarily to facilitate testing. It is hidden from users (i.e. it's only displayed with `--help-hidden`). Currently Clang doesn’t have an equivalent action. `-test-io` is used to trigger the InputOutputTest action in the Flang frontend driver. This patch makes sure that “flang-new” forwards it to “flang-new -fc1" by creating a preprocessor job. However, in Flang.cpp, `-test-io` is passed to “flang-new -fc1” without `-E`. This way we make sure that the preprocessor is _not_ run in the frontend driver. This is the desired behaviour: `-test-io` should only read the input file and print it to the output stream. co-authored-by: Andrzej Warzynski <andrzej.warzynski@arm.com> Differential Revision: https://reviews.llvm.org/D87989
2020-10-24 19:33:19 +08:00
! TEST 3: Print to a file
[flang][driver] Use --match-full-lines in tests for `-test-io` Use `--match-full-lines` to make sure that FileCheck doesn't match the output against the `CHECK` lines (which, like other comments, are also printed). More specifically, we want to make sure that the following `check` in the input file: ``` ! CHECK: <some-fortran-input> ``` is matched by FileCheck with `<some-fortran-input>` in the generated output. Without `--match-full-lines`, that check-line will be matched with `!CHECK: <some-fortran-input>` instead (which is also printed together with other contents of the file). Adding `--match-full-lines` makes the tests stricter and this change revealed that some `check`s were passing only because that flag was missing. These are updated accordingly. Reviewed By: CarolineConcatto, sameeranjoshi Differential Revision: https://reviews.llvm.org/D90306
2020-11-02 17:34:27 +08:00
! RUN: %flang-new -test-io -o %t %s 2>&1 && FileCheck %s --match-full-lines --input-file=%t
[Flang][Driver] Add infrastructure for basic frontend actions and file I/O This patch introduces the dependencies required to read and manage input files provided by the command line option. It also adds the infrastructure to create and write to output files. The output is sent to either stdout or a file (specified with the `-o` flag). Separately, in order to be able to test the code for file I/O, it adds infrastructure to create frontend actions. As a basic testable example, it adds the `InputOutputTest` FrontendAction. The sole purpose of this action is to read a file from the command line and print it either to stdout or the output file. This action is run by using the `-test-io` flag also introduced in this patch (available for `flang-new` and `flang-new -fc1`). With this patch: ``` flang-new -test-io input-file.f90 ``` will read input-file.f90 and print it in the output file. The `InputOutputTest` frontend action has been introduced primarily to facilitate testing. It is hidden from users (i.e. it's only displayed with `--help-hidden`). Currently Clang doesn’t have an equivalent action. `-test-io` is used to trigger the InputOutputTest action in the Flang frontend driver. This patch makes sure that “flang-new” forwards it to “flang-new -fc1" by creating a preprocessor job. However, in Flang.cpp, `-test-io` is passed to “flang-new -fc1” without `-E`. This way we make sure that the preprocessor is _not_ run in the frontend driver. This is the desired behaviour: `-test-io` should only read the input file and print it to the output stream. co-authored-by: Andrzej Warzynski <andrzej.warzynski@arm.com> Differential Revision: https://reviews.llvm.org/D87989
2020-10-24 19:33:19 +08:00
!----------------------------------------
! FLANG FRONTEND DRIVER (flang-new -fc1)
!----------------------------------------
! TEST 4: Write to a file (implicit)
[flang][driver] Use --match-full-lines in tests for `-test-io` Use `--match-full-lines` to make sure that FileCheck doesn't match the output against the `CHECK` lines (which, like other comments, are also printed). More specifically, we want to make sure that the following `check` in the input file: ``` ! CHECK: <some-fortran-input> ``` is matched by FileCheck with `<some-fortran-input>` in the generated output. Without `--match-full-lines`, that check-line will be matched with `!CHECK: <some-fortran-input>` instead (which is also printed together with other contents of the file). Adding `--match-full-lines` makes the tests stricter and this change revealed that some `check`s were passing only because that flag was missing. These are updated accordingly. Reviewed By: CarolineConcatto, sameeranjoshi Differential Revision: https://reviews.llvm.org/D90306
2020-11-02 17:34:27 +08:00
! RUN: %flang-new -fc1 -test-io %s 2>&1 && FileCheck %s --match-full-lines --input-file=%S/input-output-file.txt
[Flang][Driver] Add infrastructure for basic frontend actions and file I/O This patch introduces the dependencies required to read and manage input files provided by the command line option. It also adds the infrastructure to create and write to output files. The output is sent to either stdout or a file (specified with the `-o` flag). Separately, in order to be able to test the code for file I/O, it adds infrastructure to create frontend actions. As a basic testable example, it adds the `InputOutputTest` FrontendAction. The sole purpose of this action is to read a file from the command line and print it either to stdout or the output file. This action is run by using the `-test-io` flag also introduced in this patch (available for `flang-new` and `flang-new -fc1`). With this patch: ``` flang-new -test-io input-file.f90 ``` will read input-file.f90 and print it in the output file. The `InputOutputTest` frontend action has been introduced primarily to facilitate testing. It is hidden from users (i.e. it's only displayed with `--help-hidden`). Currently Clang doesn’t have an equivalent action. `-test-io` is used to trigger the InputOutputTest action in the Flang frontend driver. This patch makes sure that “flang-new” forwards it to “flang-new -fc1" by creating a preprocessor job. However, in Flang.cpp, `-test-io` is passed to “flang-new -fc1” without `-E`. This way we make sure that the preprocessor is _not_ run in the frontend driver. This is the desired behaviour: `-test-io` should only read the input file and print it to the output stream. co-authored-by: Andrzej Warzynski <andrzej.warzynski@arm.com> Differential Revision: https://reviews.llvm.org/D87989
2020-10-24 19:33:19 +08:00
! TEST 5: Write to a file (explicit)
[flang][driver] Use --match-full-lines in tests for `-test-io` Use `--match-full-lines` to make sure that FileCheck doesn't match the output against the `CHECK` lines (which, like other comments, are also printed). More specifically, we want to make sure that the following `check` in the input file: ``` ! CHECK: <some-fortran-input> ``` is matched by FileCheck with `<some-fortran-input>` in the generated output. Without `--match-full-lines`, that check-line will be matched with `!CHECK: <some-fortran-input>` instead (which is also printed together with other contents of the file). Adding `--match-full-lines` makes the tests stricter and this change revealed that some `check`s were passing only because that flag was missing. These are updated accordingly. Reviewed By: CarolineConcatto, sameeranjoshi Differential Revision: https://reviews.llvm.org/D90306
2020-11-02 17:34:27 +08:00
! RUN: %flang-new -fc1 -test-io -o %t %s 2>&1 && FileCheck %s --match-full-lines --input-file=%t
[Flang][Driver] Add infrastructure for basic frontend actions and file I/O This patch introduces the dependencies required to read and manage input files provided by the command line option. It also adds the infrastructure to create and write to output files. The output is sent to either stdout or a file (specified with the `-o` flag). Separately, in order to be able to test the code for file I/O, it adds infrastructure to create frontend actions. As a basic testable example, it adds the `InputOutputTest` FrontendAction. The sole purpose of this action is to read a file from the command line and print it either to stdout or the output file. This action is run by using the `-test-io` flag also introduced in this patch (available for `flang-new` and `flang-new -fc1`). With this patch: ``` flang-new -test-io input-file.f90 ``` will read input-file.f90 and print it in the output file. The `InputOutputTest` frontend action has been introduced primarily to facilitate testing. It is hidden from users (i.e. it's only displayed with `--help-hidden`). Currently Clang doesn’t have an equivalent action. `-test-io` is used to trigger the InputOutputTest action in the Flang frontend driver. This patch makes sure that “flang-new” forwards it to “flang-new -fc1" by creating a preprocessor job. However, in Flang.cpp, `-test-io` is passed to “flang-new -fc1” without `-E`. This way we make sure that the preprocessor is _not_ run in the frontend driver. This is the desired behaviour: `-test-io` should only read the input file and print it to the output stream. co-authored-by: Andrzej Warzynski <andrzej.warzynski@arm.com> Differential Revision: https://reviews.llvm.org/D87989
2020-10-24 19:33:19 +08:00
!-----------------------
! EXPECTED OUTPUT
!-----------------------
! CHECK-LABEL: Program arithmetic
! CHECK-NEXT: Integer :: i, j
! CHECK-NEXT: i = 2; j = 3; i= i * j;
! CHECK-NEXT: End Program arithmetic
Program arithmetic
Integer :: i, j
i = 2; j = 3; i= i * j;
[flang][driver] Use --match-full-lines in tests for `-test-io` Use `--match-full-lines` to make sure that FileCheck doesn't match the output against the `CHECK` lines (which, like other comments, are also printed). More specifically, we want to make sure that the following `check` in the input file: ``` ! CHECK: <some-fortran-input> ``` is matched by FileCheck with `<some-fortran-input>` in the generated output. Without `--match-full-lines`, that check-line will be matched with `!CHECK: <some-fortran-input>` instead (which is also printed together with other contents of the file). Adding `--match-full-lines` makes the tests stricter and this change revealed that some `check`s were passing only because that flag was missing. These are updated accordingly. Reviewed By: CarolineConcatto, sameeranjoshi Differential Revision: https://reviews.llvm.org/D90306
2020-11-02 17:34:27 +08:00
End Program arithmetic