We apply special symbol table scoping to top-level subroutine
and function names that have interoperable binding names, so
that it's possible to define the same subroutine/function name
more than once at the top level so long as their binding names
are distinct. But we don't use those scoping techniques for
ENTRY statement symbols with interoperable binding names,
which can lead to bogus semantic errors when the same ENTRY
name is defined multiple times with distinct binding names.
Details
Details
Diff Detail
Diff Detail
Event Timeline
Comment Actions
Apart from the extra empty statement in resolve-names.cpp, all builds and tests correctly and looks good.
flang/lib/Semantics/resolve-names.cpp | ||
---|---|---|
3512 | This looks spurious. |
This looks spurious.