diff options
| author | Peter Klausler <35819229+klausler@users.noreply.github.com> | 2024-09-04 10:54:46 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-09-04 10:54:46 -0700 |
| commit | d1e4a2d300f7c0c6b681ddf719132c81d348aaab (patch) | |
| tree | 61c7f9b6edcf80ba746e2d41c6393c280931de3c /lldb/source/Plugins/ScriptInterpreter/Python/Interfaces/ScriptedProcessPythonInterface.cpp | |
| parent | 840da2e8ba7e0f77938adfc6f6d315137542a1b8 (diff) | |
[flang] Fix spurious error with separate module procedures (#106768)
When the implementation of one SMP apparently references another in what
might be a specification expression, semantics may need to resolve it as
a forward reference, and to allow for the replacement of a
SubprogramNameDetails place-holding symbol with the final
SubprogramDetails symbol. Otherwise, as in the bug report below,
confusing error messages may result.
(The reference in question isn't really in the specification part of a
subprogram, but due to the syntactic ambiguity between the array element
assignment statement and a statement function definition, it appears to
be so at the time that the reference is processed.)
I needed to make DumpSymbols() available via SemanticsContext to analyze
this bug, and left that new API in place to make things easier next
time.
Fixes https://github.com/llvm/llvm-project/issues/106705.
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/Interfaces/ScriptedProcessPythonInterface.cpp')
0 files changed, 0 insertions, 0 deletions