[all-commits] [llvm/llvm-project] 79caf6: [flang] Runtime implementation for default derived...

[Peter Klausler via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 79caf69cc08a72022f968020eab486b698fd4178
      https://github.com/llvm/llvm-project/commit/79caf69cc08a72022f968020eab486b698fd4178
  Author: peter klausler <pklausler at nvidia.com>
  Date:   2021-06-18 (Fri, 18 Jun 2021)

  Changed paths:
    M flang/include/flang/Semantics/runtime-type-info.h
    M flang/lib/Semantics/runtime-type-info.cpp
    M flang/runtime/CMakeLists.txt
    M flang/runtime/copy.cpp
    M flang/runtime/derived.cpp
    M flang/runtime/descriptor-io.h
    M flang/runtime/descriptor.cpp
    M flang/runtime/descriptor.h
    M flang/runtime/namelist.cpp
    M flang/runtime/tools.h
    A flang/runtime/type-info.cpp
    M flang/runtime/type-info.h
    M flang/test/Semantics/typeinfo01.f90

  Log Message:
  -----------
  [flang] Runtime implementation for default derived type formatted I/O

This is *not* user-defined derived type I/O, but rather Fortran's
built-in capabilities for using derived type data in I/O lists
and NAMELIST groups.

This feature depends on having the derived type description tables
that are created by Semantics available, passed through compilation
as initialized static objects to which pointers can be targeted
in the descriptors of I/O list items and NAMELIST groups.

NAMELIST processing now handles component references on input
(e.g., "&GROUP x%component = 123 /").

The C++ perspectives of the derived type information records
were transformed into proper classes when it was necessary to add
member functions to them.

The code in Semantics that generates derived type information
was changed to emit derived type components in component order,
not alphabetic order.

Differential Revision: https://reviews.llvm.org/D104485