diff options
| author | Peter Klausler <pklausler@nvidia.com> | 2025-09-30 10:34:41 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-09-30 10:34:41 -0700 |
| commit | 2780c209e1e242fd9e7d71045f88fe4e824cee20 (patch) | |
| tree | 6633ebd7ecd5350435a8a63baa79217ac7a2946c /lldb/packages/Python/lldbsuite/test/configuration.py | |
| parent | ee8394d9469a2946ffe2e7d192c593ecf3f93098 (diff) | |
| download | llvm-2780c209e1e242fd9e7d71045f88fe4e824cee20.zip llvm-2780c209e1e242fd9e7d71045f88fe4e824cee20.tar.gz llvm-2780c209e1e242fd9e7d71045f88fe4e824cee20.tar.bz2 | |
[flang] Emit error on impossible-to-implement construct (#160384)
An assignment to a whole polymorphic allocatable changes its dynamic
type to the type of the right-hand side expression. But when the
assignment is under control of a WHERE statement, or a FORALL / DO
CONCURRENT with a mask expression, there is no interpretation of the
assignment, as the type of a variable must be the same for all of its
elements.
There is no restriction in the standard against this usage, and no other
Fortran compiler complains about it. But it is not possible to implement
it in general, and the behavior produced by other compilers is not
reasonable, much less worthy of emulating. It's best to simply disallow
it with an error message.
Fixes https://github.com/llvm/llvm-project/issues/133669, or more
accurately, resolves it.
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/configuration.py')
0 files changed, 0 insertions, 0 deletions