summaryrefslogtreecommitdiff
path: root/lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.cpp
diff options
context:
space:
mode:
authorPeter Klausler <pklausler@nvidia.com>2025-04-18 12:48:55 -0700
committerGitHub <noreply@github.com>2025-04-18 12:48:55 -0700
commit46387cd18420e120bbcfa3a646d48e2903a5c28c (patch)
treef09af7dcf61f3deeb8145c38f368b20c067d6eca /lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.cpp
parent21a406c92c6cd79116a03443bccc47c1700d73db (diff)
[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.)
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.cpp')
0 files changed, 0 insertions, 0 deletions