diff options
| author | peter klausler <pklausler@nvidia.com> | 2021-01-12 15:36:45 -0800 |
|---|---|---|
| committer | peter klausler <pklausler@nvidia.com> | 2021-01-13 10:05:14 -0800 |
| commit | a50bb84ec0c2d47a2a7403ad29842ca48cd6b828 (patch) | |
| tree | 8434c63da1f7a549c2514cb70eeaa84083ac5e55 /llvm/lib/Support/Program.cpp | |
| parent | 14f322f074b933af1e26bf6288b88ec2e7c3a551 (diff) | |
| download | llvm-a50bb84ec0c2d47a2a7403ad29842ca48cd6b828.zip llvm-a50bb84ec0c2d47a2a7403ad29842ca48cd6b828.tar.gz llvm-a50bb84ec0c2d47a2a7403ad29842ca48cd6b828.tar.bz2 | |
[flang] Fix classification of shape inquiries in specification exprs
In some contexts, including the motivating case of determining whether
the expressions that define the shape of a variable are "constant expressions"
in the sense of the Fortran standard, expression rewriting via Fold()
is not necessary, and should not be required. The inquiry intrinsics LBOUND,
UBOUND, and SIZE work correctly now in specification expressions and are
classified correctly as being constant expressions (or not). Getting this right
led to a fair amount of API clean-up as a consequence, including the
folding of shapes and TypeAndShape objects, and new APIs for shapes
that do not fold for those cases where folding isn't needed. Further,
the symbol-testing predicate APIs in Evaluate/tools.h now all resolve any
associations of their symbols and work transparently on use-, host-, and
construct-association symbols; the tools used to resolve those associations have
been defined and documented more precisely, and their clients adjusted as needed.
Differential Revision: https://reviews.llvm.org/D94561
Diffstat (limited to 'llvm/lib/Support/Program.cpp')
0 files changed, 0 insertions, 0 deletions