diff options
| author | Peter Klausler <35819229+klausler@users.noreply.github.com> | 2023-12-26 16:03:03 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-12-26 16:03:03 -0800 |
| commit | 5a402c56226e9b50bffdedd19d2acb8b61b408a3 (patch) | |
| tree | 9aa2a0d0cf6f2fdc861986ba3ff8a400effe7811 /llvm/lib/Target/RISCV/Disassembler/RISCVDisassembler.cpp | |
| parent | c86fe3ee0b92934f5d18394d9a0cdc1d3f0eef64 (diff) | |
| download | llvm-5a402c56226e9b50bffdedd19d2acb8b61b408a3.zip llvm-5a402c56226e9b50bffdedd19d2acb8b61b408a3.tar.gz llvm-5a402c56226e9b50bffdedd19d2acb8b61b408a3.tar.bz2 | |
[flang] USE-associated explicit INTRINSIC names (#76199)
The compiler doesn't USE-associate names of intrinsic procedures from
modules (in the absence of ONLY:), so that the associating scope doesn't
get populated with names of intrinsics that were used only in
declarations (e.g., SELECTED_REAL_KIND). A recent bug report (below)
shows that we should modify that policy in the case of names that appear
in explicit INTRINSIC attribute statements. The behaviors of other
Fortran compilers are not consistent and the requirements of the
standard are not clear; this fix follows the precedent set by gfortran
and nvfortran.
Fixes https://github.com/llvm/llvm-project/issues/72084.
Diffstat (limited to 'llvm/lib/Target/RISCV/Disassembler/RISCVDisassembler.cpp')
0 files changed, 0 insertions, 0 deletions