aboutsummaryrefslogtreecommitdiff
path: root/lldb/packages/Python/lldbsuite/test/gdbclientutils.py
diff options
context:
space:
mode:
authorPeter Klausler <pklausler@nvidia.com>2025-09-30 10:36:10 -0700
committerGitHub <noreply@github.com>2025-09-30 10:36:10 -0700
commit10a9ec88501fa260002245fcd4d0c6f6ccae4e17 (patch)
tree34600e3d451465d31c150a5c668ce153a3ed8df5 /lldb/packages/Python/lldbsuite/test/gdbclientutils.py
parent2c58d192a2a6e54080ac36e0626487747dc7be5c (diff)
downloadllvm-10a9ec88501fa260002245fcd4d0c6f6ccae4e17.zip
llvm-10a9ec88501fa260002245fcd4d0c6f6ccae4e17.tar.gz
llvm-10a9ec88501fa260002245fcd4d0c6f6ccae4e17.tar.bz2
[flang] Fix crash in structure constructor lowering (#160769)
MLIR types created by lowering for structure constructors appear to be sensitive to the ordering of their components in the typed expression representation used for structure constructors and derived type constant values. At present, the components appear in source position order. When some ancestral types are defined in modules, this ordering can cause their components to be ordered after components defined in extended derived types. This can lead to crashes from incompatible MLIR types. To avoid this issue, sort structure constructor components first in ascending order of derived type extension depth; retain source position ordering for components in the same derived type and for error recovery situations. Fixes https://github.com/llvm/llvm-project/issues/143740.
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/gdbclientutils.py')
0 files changed, 0 insertions, 0 deletions