diff options
| author | Peter Klausler <pklausler@nvidia.com> | 2023-02-15 11:11:54 -0800 |
|---|---|---|
| committer | Peter Klausler <pklausler@nvidia.com> | 2023-02-15 12:05:12 -0800 |
| commit | ee437afa912b2608dad783225ec8e98d98f5a084 (patch) | |
| tree | 5b61292fb0a4c276bcfc3bbf196859916f8492f0 /lldb/source/Plugins/ScriptInterpreter/Python | |
| parent | 6f3e6a765a9e9ba4fa6a991980355b0ef9007052 (diff) | |
| download | llvm-ee437afa912b2608dad783225ec8e98d98f5a084.zip llvm-ee437afa912b2608dad783225ec8e98d98f5a084.tar.gz llvm-ee437afa912b2608dad783225ec8e98d98f5a084.tar.bz2 | |
[flang] Don't add a source range to a type instantiation's scope
A type instantiation's scope doesn't require a source range, as we don't
need/want it to be the result of SemanticsContext::FindScope(), and
adding the original type's source range to the scope of one of its
instantiations has the side effect of expanding the source range of
all of its parents to include the original type definition, which
breaks FindScope() for any scope including a type instantiation.
Differential Revision: https://reviews.llvm.org/D144129
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python')
0 files changed, 0 insertions, 0 deletions