diff options
author | Peter Klausler <pklausler@nvidia.com> | 2025-09-30 10:36:52 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2025-09-30 10:36:52 -0700 |
commit | ed5e6b87013485c7b16d825e0cbf556a1e7e3e19 (patch) | |
tree | 3ebb14e9b1c16b677f204c281dd235e469e666ef /lldb/packages/Python/lldbsuite/test/gdbclientutils.py | |
parent | 52afb8dd112d52b620003998b5348b45b214e828 (diff) | |
download | llvm-ed5e6b87013485c7b16d825e0cbf556a1e7e3e19.zip llvm-ed5e6b87013485c7b16d825e0cbf556a1e7e3e19.tar.gz llvm-ed5e6b87013485c7b16d825e0cbf556a1e7e3e19.tar.bz2 |
[flang] Catch calls to impure intrinsics from PURE subprograms (#160947)
The code in expression semantics that catches a call to an impure
procedure in a PURE context misses calls to impure intrinsics, since
their designators have a SpecificIntrinsic rather than a Symbol. Replace
the current check with a new one that uses the characteristics of the
called procedure, which works for both intrinsic and non-intrinsic
cases.
Testing this change revealed that an explicit INTRINSIC statement wasn't
doing the right thing for extension "dual" intrinsics that can be called
as either a function or as a subroutine; the use of an INTRINSIC
statement would disallow its use as a subroutine. I've fixed that here
as well.
Fixes https://github.com/llvm/llvm-project/issues/157124.
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/gdbclientutils.py')
0 files changed, 0 insertions, 0 deletions