diff options
| author | Peter Klausler <pklausler@nvidia.com> | 2025-01-08 13:14:02 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-01-08 13:14:02 -0800 |
| commit | 07b3bba901e7d51b3173631d6af811eae9d84cda (patch) | |
| tree | cd3f51b7db71a1c8880f5267c5a4066bf4499a85 /llvm/lib/ProfileData/Coverage/CoverageMapping.cpp | |
| parent | 94963919011d77c2f3f9d867cb73067a4f50e87c (diff) | |
| download | llvm-07b3bba901e7d51b3173631d6af811eae9d84cda.zip llvm-07b3bba901e7d51b3173631d6af811eae9d84cda.tar.gz llvm-07b3bba901e7d51b3173631d6af811eae9d84cda.tar.bz2 | |
[flang] Allow LOCK_TYPE & al. to associate with INTENT(IN OUT) (#121413)
We're emitting a bogus semantic error message about an actual argument
being undefinable when associating LOCK_TYPE, EVENT_TYPE, and someday
NOTIFY_TYPE with an INTENT(IN OUT) dummy argument. These types indeed
make many definition contexts invalid, and the actual argument
associated with an INTENT(IN OUT) dummy argument must indeed be
definable, but the argument association itself is not a problem.
Diffstat (limited to 'llvm/lib/ProfileData/Coverage/CoverageMapping.cpp')
0 files changed, 0 insertions, 0 deletions