d18a9aeae9
With this change, the following invocations will be treated as errors (multiple actions are specified): ``` $ flang-new -fc1 -E -fsyntax-only file.95 $ flang-new -fc1 -fsyntax-only -fdebug-dump-symbols file.95 ``` In the examples above it is not clear whether it is `-fsyntax-only` or the other action that is run (i.e. `-E` or `-fdebug-dump-symbols`). It makes sense to disallow such usage. This should also lead to cleaner and clearer tests (the `RUN` lines using `%flang_fc1` will only allow one action). This change means that `flang-new -fc1` and `clang -cc1` will behave differently when multiple action options are specified. As frontend drivers are mostly used by compiler developers, this shouldn't affect or confuse the compiler end-users. Also, `flang-new` and `clang` remain consistent. Tests are updated accordingly. More specifically, I've made sure that every test specifies only one action. I've also taken the opportunity to simplify "multiple-input-files.f90" a bit. Differential Revision: https://reviews.llvm.org/D111781
20 lines
516 B
Fortran
20 lines
516 B
Fortran
! Tests -fget-symbols-sources with BLOCK that contains same variable name as
|
|
! another in an outer scope.
|
|
program main
|
|
integer :: x
|
|
integer :: y
|
|
block
|
|
integer :: x
|
|
integer :: y
|
|
x = y
|
|
end block
|
|
x = y
|
|
end program
|
|
|
|
!! Inner x
|
|
! RUN: %flang_fc1 -fget-definition 9 5 6 %s | FileCheck --check-prefix=CHECK1 %s
|
|
! CHECK1: x:{{.*}}getdefinition05.f90, 7, 16-17
|
|
!! Outer y
|
|
! RUN: %flang_fc1 -fget-definition 11 7 8 %s | FileCheck --check-prefix=CHECK2 %s
|
|
! CHECK2: y:{{.*}}getdefinition05.f90, 5, 14-15
|