diff options
| author | Peter Klausler <pklausler@nvidia.com> | 2022-07-22 10:52:30 -0700 |
|---|---|---|
| committer | Peter Klausler <pklausler@nvidia.com> | 2022-07-22 16:54:46 -0700 |
| commit | e03664d40c707017dc5bab16be19d6939b5719d2 (patch) | |
| tree | 79797396f51952528a194dc997e08daebe1e4dd8 /lldb/source/Plugins/ScriptInterpreter/Python/lldb-python.h | |
| parent | 0d89963df354ee309c15f67dc47c8ab3cb5d0fb2 (diff) | |
| download | llvm-e03664d40c707017dc5bab16be19d6939b5719d2.zip llvm-e03664d40c707017dc5bab16be19d6939b5719d2.tar.gz llvm-e03664d40c707017dc5bab16be19d6939b5719d2.tar.bz2 | |
[flang] Fix parsing and semantics for array element substring%KIND/%LEN
A type-param-inquiry of %KIND or %LEN applies to a designator, and
so must also be allowed for a substring. F18 presently (mis)parses
instances of a type-param-inquiry as structure component references
and then fixes them in expression semantics when types are known and
we can distinguish them. But when the base of a type-param-inquiry is
a substring of an array element, as in "charArray(i)(j:k)%len",
parsing fails.
Adjust the grammar to parse these cases, and extend expression semantics
to process the new production.
Differential Revision: https://reviews.llvm.org/D130375
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/lldb-python.h')
0 files changed, 0 insertions, 0 deletions