diff options
| author | Peter Klausler <pklausler@nvidia.com> | 2022-07-18 10:27:05 -0700 |
|---|---|---|
| committer | Peter Klausler <pklausler@nvidia.com> | 2022-07-25 10:09:55 -0700 |
| commit | 85a40ce6ddf6abf06886dc594aeb998e05f75faa (patch) | |
| tree | d1620d10686a8f03e7ae24165cef4efa710d12d9 /llvm/docs/tutorial | |
| parent | 2c84b92346bc45a88f92d781e30daa8490049c4d (diff) | |
| download | llvm-85a40ce6ddf6abf06886dc594aeb998e05f75faa.zip llvm-85a40ce6ddf6abf06886dc594aeb998e05f75faa.tar.gz llvm-85a40ce6ddf6abf06886dc594aeb998e05f75faa.tar.bz2 | |
[flang] Better error message for NULL() actual argument for dummy allocatable
f18 intentionally does not support the spottily-implemented language extension
in which one can pass NULL() for an allocatable dummy argument. This is perhaps
a sanctioned side effect in other compilers of the fact that they pass distinct
"base address" and "descriptor address" physical arguments.
Make the error message in this case more specific to the circumstances, and
add a note to Extensions.md to clarify that this behavior is intended.
(We could, with some effort in lowering, support passing NULL for an INTENT(IN)
allocatable dummy, but let's see whether such nonconforming usage appears
in a real application before spending any more time on it.)
Differential Revision: https://reviews.llvm.org/D130380
Diffstat (limited to 'llvm/docs/tutorial')
0 files changed, 0 insertions, 0 deletions