[all-commits] [llvm/llvm-project] caa0a2: [flang] Add warnings about undefinable actuals for...

[Peter Klausler via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: caa0a2695e6caa4da088f6f933ac45839d425656
      https://github.com/llvm/llvm-project/commit/caa0a2695e6caa4da088f6f933ac45839d425656
  Author: Peter Klausler <35819229+klausler at users.noreply.github.com>
  Date:   2024-06-03 (Mon, 03 Jun 2024)

  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/call03.f90
    M flang/test/Semantics/call30.f90

  Log Message:
  -----------
  [flang] Add warnings about undefinable actuals for ASYNCHRONOUS/VOLAT… (#93851)

…ILE dummies

There's language in the standard (F'2023 15.5.2.5 p21) disallowing an
actual argument with a vector subscript from associating with a dummy
argument with either the ASYNCHRONOUS or VOLATILE attributes. This is a
bug in the standard, as (1) these attributes are actually relevant only
over the scope of the called procedure, (2) they can be applied in
nested scopes (internal subprograms and BLOCK) within the called
procedure, and (3) can be implicit within the called procedure and its
nested scopes in the case of ASYNCHRONOUS as a side effect of using a
dummy argument in an asynchronous data transfer statement. So issue a
warning. This new warning about undefinable actual arguments being
associated with ASYNCHRONOUS and VOLATILE dummy arguments subsumes an
existing warning about passing a constant actual to a VOLATILE dummy.

Resolves https://github.com/llvm/llvm-project/issues/93600.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications