llvm-capstone/flang
jeanPerier d26c78b2ad
[flang] handle indirect module variable use in internal procedure (#65324)
When a module variable is referenced inside an internal procedure, but
the use statement for the module is inside the host, semantics may not
create any symbols with HostAssocDetails directly under the internal
procedure scope.
So pft::getScopeVariableList, that is called in the bridge when lowering
the internal procedure scope, failed to instantiate the module
variables. This lead to "symbol is not mapped to any IR value" compile
time errors.

This patch fixes the issue by adding the variables to the list of
"captured" global variables from the host program, so that they are
instantiated as part of the `internalProcedureBindings` in the bridge.

The rational of doing it that way instead of changing
`getScopeVariableList` is that `getScopeVariableList` would have to
import all the module variables used inside the host since it cannot
know which ones are referenced inside the internal procedure from the
semantics::Scope information. The fix in this patch only instantiates
the module variables from the host that are actually referenced inside
the internal procedure.
2023-09-06 09:07:45 +02:00
..
cmake/modules [flang] Refine how Clang dependencies are expressed #58663 2023-04-16 17:44:25 +00:00
docs [flang][openacc] Relax required clauses on acc data as portability warning 2023-08-29 14:57:50 -07:00
examples [flang] Bump python dependencies in flang/examples/FlangOmpReport 2023-08-07 18:00:07 +01:00
include [flang] Fix duplicate word typos; NFC 2023-09-01 18:41:05 -07:00
lib [flang] handle indirect module variable use in internal procedure (#65324) 2023-09-06 09:07:45 +02:00
module [flang] Adding two more PowerPC MMA intrinsics 2023-08-21 11:00:19 -04:00
runtime [flang] Allow runtime build with AVOID_NATIVE_INT128_T=1 2023-09-01 08:54:38 -07:00
test [flang] handle indirect module variable use in internal procedure (#65324) 2023-09-06 09:07:45 +02:00
tools [Driver] Refactor to use llvm Option's new Visibility flags 2023-08-15 14:26:40 -07:00
unittests [flang] Improved performance of runtime Matmul/MatmulTranspose. 2023-08-29 17:04:00 -07:00
.clang-format
.clang-tidy
.drone.star
.gitignore
CMakeLists.txt [flang] Fix for 541f5c4a6d (D140524) breaking out-of-tree flang build. 2023-06-03 15:19:01 +02:00
CODE_OWNERS.TXT [Flang] Add code owner for the Driver 2023-04-14 14:38:32 +00:00
LICENSE.TXT
README.md [Flang][Docs] Add a GettingStarted.md for build instructions 2023-04-12 23:33:48 +05:30

Flang

Flang is a ground-up implementation of a Fortran front end written in modern C++. It started off as the f18 project (https://github.com/flang-compiler/f18) with an aim to replace the previous flang project (https://github.com/flang-compiler/flang) and address its various deficiencies. F18 was subsequently accepted into the LLVM project and rechristened as Flang.

Please note that flang is not ready yet for production usage.

Getting Started

Read more about flang in the docs directory. Start with the compiler overview.

To better understand Fortran as a language and the specific grammar accepted by flang, read Fortran For C Programmers and flang's specifications of the Fortran grammar and the OpenMP grammar.

Treatment of language extensions is covered in this document.

To understand the compilers handling of intrinsics, see the discussion of intrinsics.

To understand how a flang program communicates with libraries at runtime, see the discussion of runtime descriptors.

If you're interested in contributing to the compiler, read the style guide and also review how flang uses modern C++ features.

If you are interested in writing new documentation, follow LLVM's Markdown style guide.

Consult the Getting Started with Flang for information on building and running flang.