diff options
| author | Peter Klausler <pklausler@nvidia.com> | 2025-10-10 10:09:33 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-10-10 10:09:33 -0700 |
| commit | 471ed9ad6251429253c9441eadff87439a2fbfb7 (patch) | |
| tree | 01543295c5ec8fda7505aadf95d296c6fe0eca79 /lldb/source/Plugins/ScriptInterpreter/Python/lldb-python.h | |
| parent | e2ee91ed34207859fa6afaaf0573bdf1396e7f27 (diff) | |
| download | llvm-471ed9ad6251429253c9441eadff87439a2fbfb7.zip llvm-471ed9ad6251429253c9441eadff87439a2fbfb7.tar.gz llvm-471ed9ad6251429253c9441eadff87439a2fbfb7.tar.bz2 | |
[flang] Rework component KIND= values in PDT instantiations (#162367)
When processing the KIND= values of type specifications in parameterized
derived type component declarations, it turns out to be necessary to
analyze their expressions' parse trees rather than to just fold their
typed expression representations. The types of the subexpressions may
depend on the values of KIND parameters.
Further, when checking the values of KIND= actual arguments to type
conversion intrinsic functions (e.g., INT(..., KIND=)) that appear in
KIND specifiers for PDT component declarations, don't emit an error for
the derived type definition, but instead emit them for derived type
instantiations.
Fixes https://github.com/llvm/llvm-project/issues/161961.
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/lldb-python.h')
0 files changed, 0 insertions, 0 deletions