[all-commits] [llvm/llvm-project] 61d361: [flang] Extension: accept NULL([MOLD=]) for ALLOCA...

Peter Klausler via All-commits all-commits at lists.llvm.org
Mon Sep 18 12:38:00 PDT 2023


  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 61d361d69bb3af183b63be3e8a7056030e92de8a
      https://github.com/llvm/llvm-project/commit/61d361d69bb3af183b63be3e8a7056030e92de8a
  Author: Peter Klausler <35819229+klausler at users.noreply.github.com>
  Date:   2023-09-18 (Mon, 18 Sep 2023)

  Changed paths:
    M flang/docs/Extensions.md
    M flang/include/flang/Common/Fortran-features.h
    M flang/lib/Semantics/check-call.cpp
    M flang/test/Semantics/call27.f90

  Log Message:
  -----------
  [flang] Extension: accept NULL([MOLD=]) for ALLOCATABLE INTENT(IN) du… (#66256)

…mmy argument

Several compilers accept a null pointer (with or without a MOLD=) as an
actual argument for association with an INTENT(IN) allocatable dummy
argument. At runtime, the allocatable dummy argument appears to be in
the unallocated state. This seems useful, unambiguous, unlikely to
invalidate conforming code, and works with Intel, NAG, & XLF, so it
should be supported with an optional portability warning in this
compiler as well.




More information about the All-commits mailing list