llvm-project/flang/test/Driver/parse-error.f95

! Verify that parsing errors are correctly reported by the driver

! RUN: not %flang_fc1 -fsyntax-only %s 2>&1 | FileCheck %s --check-prefix=ERROR

! ERROR: Could not parse {{.*}}parse-error.f95

"This file will not parse"
[flang][driver] Remove `%flang-new` from the LIT configuration `%flang-new` was introduced in the early days of the new driver to make a clear distinction between the tests for the current and the new driver. We have since introduced `%flang` (compiler driver) and `%flang_fc1` (frontend driver) as the long term solution. This has allowed us to share tests between `flang-new` and `f18`. This patch replaces all uses of `%flang-new` with `%flang` and `%flang_fc1`. Some tests are reformatted so that all tests look uniform and are easier to follow. Where possible, `! REQUIRES: new-flang-driver` is deleted so that more tests can be shared with `f18`. To facilitate this, `f{no-}implicit-none` are introduced in `f18` with semantics identical to `flang-new`. Two tests are deleted rather than updated: * flang/test/Frontend/print-preprocess-C-file.f90 * flang/test/Frontend/print-preprocessed-file.f90 Instead, there is plenty of preprocessor tests in flang/test/Preprocessing/. Differential Revision: https://reviews.llvm.org/D100174 2021-04-09 18:32:31 +08:00			`! Verify that parsing errors are correctly reported by the driver`
[flang][driver] Add checks for errors from `Prescan` and `Parse` If either `Prescan` or `Parse` generate any fatal errors, the new driver will: * report it (i.e. issue an error diagnostic) * exit early * return non-zero exit code This behaviour is consistent with f18 (i.e. the old driver). Reviewed By: sameeranjoshi Differential Revision: https://reviews.llvm.org/D93712 2021-01-06 17:54:30 +08:00
[flang][driver] Remove `%flang-new` from the LIT configuration `%flang-new` was introduced in the early days of the new driver to make a clear distinction between the tests for the current and the new driver. We have since introduced `%flang` (compiler driver) and `%flang_fc1` (frontend driver) as the long term solution. This has allowed us to share tests between `flang-new` and `f18`. This patch replaces all uses of `%flang-new` with `%flang` and `%flang_fc1`. Some tests are reformatted so that all tests look uniform and are easier to follow. Where possible, `! REQUIRES: new-flang-driver` is deleted so that more tests can be shared with `f18`. To facilitate this, `f{no-}implicit-none` are introduced in `f18` with semantics identical to `flang-new`. Two tests are deleted rather than updated: * flang/test/Frontend/print-preprocess-C-file.f90 * flang/test/Frontend/print-preprocessed-file.f90 Instead, there is plenty of preprocessor tests in flang/test/Preprocessing/. Differential Revision: https://reviews.llvm.org/D100174 2021-04-09 18:32:31 +08:00			`! RUN: not %flang_fc1 -fsyntax-only %s 2>&1 \| FileCheck %s --check-prefix=ERROR`
[flang][driver] Add checks for errors from `Prescan` and `Parse` If either `Prescan` or `Parse` generate any fatal errors, the new driver will: * report it (i.e. issue an error diagnostic) * exit early * return non-zero exit code This behaviour is consistent with f18 (i.e. the old driver). Reviewed By: sameeranjoshi Differential Revision: https://reviews.llvm.org/D93712 2021-01-06 17:54:30 +08:00
[flang][driver] Update error messages (nfc) As per Flang's coding guidelines (flang/docs/C++style.md#error-messages): ``` Messages should start with a capital letter. ``` This patch updates error messages in the driver (new and old) so that they conform with the guideline above. This change was suggested in one of the recent reviews: https://reviews.llvm.org/D93712. It felt like this deserved a dedicated patch, so sending it separately. 2021-01-06 18:35:00 +08:00			`! ERROR: Could not parse {{.*}}parse-error.f95`
[flang][driver] Add checks for errors from `Prescan` and `Parse` If either `Prescan` or `Parse` generate any fatal errors, the new driver will: * report it (i.e. issue an error diagnostic) * exit early * return non-zero exit code This behaviour is consistent with f18 (i.e. the old driver). Reviewed By: sameeranjoshi Differential Revision: https://reviews.llvm.org/D93712 2021-01-06 17:54:30 +08:00
			`"This file will not parse"`