[all-commits] [llvm/llvm-project] 46387c: [flang] Compile the output of -fdebug-unparse-with...

[Peter Klausler via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 46387cd18420e120bbcfa3a646d48e2903a5c28c
      https://github.com/llvm/llvm-project/commit/46387cd18420e120bbcfa3a646d48e2903a5c28c
  Author: Peter Klausler <pklausler at nvidia.com>
  Date:   2025-04-18 (Fri, 18 Apr 2025)

  Changed paths:
    M flang/docs/ModFiles.md
    M flang/lib/Semantics/resolve-names.cpp
    M flang/test/Semantics/resolve11.f90

  Log Message:
  -----------
  [flang] Compile the output of -fdebug-unparse-with-modules (#135696)

The output of a compilation with the -fdebug-unparse-with-modules option
comprises its normal unparsed output along with the regenerated contents
of any modules that were required from module files. This is handy for
producing stand-alone test cases.

The modules' contents are generated by the same code that writes module
files, so they can contain some USE associations to private entities in
other modules that are necessary to complete local declarations, usually
initializers. Such USE associations to private entities are not flagged
as fatal errors when modules are read from module files, but they
currently are caught when the output produced by this option is being
read back in to the compiler.

Handle this case by softening the error to a warning when one module
uses a private entity from another with an alias containing the
non-conforming '$' character. (I could have omitted the message
altogether, but there are other valid warnings that will occur due to
undefined function result variables; further, I didn't want to provide a
general hole around the protection of private names.)



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