llvm-project/flang/test/Semantics/getsymbols04.f90

! Tests -fget-symbols-sources with COMMON.
program main
  integer :: x
  integer :: y
  common /x/ y
  x = y
end program

! RUN: %flang_fc1 -fget-symbols-sources %s 2>&1 | FileCheck %s
! CHECK:x:{{.*}}getsymbols04.f90, 3, 14-15
! CHECK:x:{{.*}}getsymbols04.f90, 5, 11-12
! CHECK:y:{{.*}}getsymbols04.f90, 4, 14-15
[flang] FindOffsetLineAndColumn also uses SourcePosition. New tests for COMMON and BLOCK. Added CHECK-ONCE to test_any.sh. Make sure pattern only occurs once. Original-commit: flang-compiler/f18@ad82dafcf905c521904a0120462ad1636917fc8c Reviewed-on: https://github.com/flang-compiler/f18/pull/698 Tree-same-pre-rewrite: false 2019-09-06 01:05:45 +08:00			`! Tests -fget-symbols-sources with COMMON.`
			`program main`
			`integer :: x`
			`integer :: y`
			`common /x/ y`
			`x = y`
			`end program`

[flang] Make the frontend driver error out when requesting multiple actions 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 2021-10-14 16:07:30 +08:00			`! RUN: %flang_fc1 -fget-symbols-sources %s 2>&1 \| FileCheck %s`
[flang] Port test_any.sh tests to FileCheck: Hand port getsymbols tests test_any.sh's FileCheck accepts the CHECK line matches in any order while FileCheck checks in strict order. Re-order the CHECK lines to source code order - they come from an ordered datastructure. Some CHECK lines are sensitive to line number which are fixed up manually. getsymbols02 had multiple test inputs which had their own EXEC lines. Consolidate these together in one file. Differential Revision: https://reviews.llvm.org/D82166 2020-06-27 01:49:21 +08:00			`! CHECK:x:{{.*}}getsymbols04.f90, 3, 14-15`
			`! CHECK:x:{{.*}}getsymbols04.f90, 5, 11-12`
[flang] Make -fget-symbols-sources output deterministic The DumpSymbolsSources() routine ordered its output by the addresses of the names of the symbols, and was susceptible to variation across environments. Fixed by using a multimap using the values of the names. Differential Revision: https://reviews.llvm.org/D87035 2020-09-02 07:55:43 +08:00			`! CHECK:y:{{.*}}getsymbols04.f90, 4, 14-15`