diff options
| author | Peter Klausler <pklausler@nvidia.com> | 2022-01-28 08:28:00 -0800 |
|---|---|---|
| committer | Peter Klausler <pklausler@nvidia.com> | 2022-02-02 10:49:10 -0800 |
| commit | 73f21db537f7828ab55bd2a365e5ccdf2c439ab7 (patch) | |
| tree | bd7e7600467a26a2e05bb9dcb3fca928c58c1cf5 /clang/lib/Frontend/PrintPreprocessedOutput.cpp | |
| parent | 0b5fb7c604e66b04b66b0bedb8141941a6237551 (diff) | |
| download | llvm-73f21db537f7828ab55bd2a365e5ccdf2c439ab7.zip llvm-73f21db537f7828ab55bd2a365e5ccdf2c439ab7.tar.gz llvm-73f21db537f7828ab55bd2a365e5ccdf2c439ab7.tar.bz2 | |
[flang] Fix: use right symbol for parent component
When constructing the representation for a component reference
to an inherited component, expression semantics make the parent
component references explicit in the DataRef; e.g., base%component
becomes base%parent%grandparent%component if component was
inheritance-associated through two levels. But expression semantics
was inserting references to the symbol table entries for the
intermediate types, not the symbols for the parent components in
the extended types. (We didn't notice the distinction until
recently because both symbols have the same name; this only
affects lowering.) Find and use the right symbols.
Differential Revision: https://reviews.llvm.org/D118746
Diffstat (limited to 'clang/lib/Frontend/PrintPreprocessedOutput.cpp')
0 files changed, 0 insertions, 0 deletions