[llvm-bugs] [Bug 48648] New: Module: private variables are exposed to the outside world

[via llvm-bugs]

https://bugs.llvm.org/show_bug.cgi?id=48648

            Bug ID: 48648
           Summary: Module: private variables are exposed to the outside
                    world
           Product: flang
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P
         Component: Frontend
          Assignee: unassignedbugs at nondot.org
          Reporter: howisjw at hotmail.com
                CC: David.Truby at arm.com, jperier at nvidia.com,
                    kirankumartp at gmail.com, llvm-bugs at lists.llvm.org,
                    sscalpone at nvidia.com

Created attachment 24337
  --> https://bugs.llvm.org/attachment.cgi?id=24337&action=edit
module private bug

Hello,

I am testing the new Fortran front-end, which has been built from source using
LLVM 11.0.0 release. While testing I encountered a bug related the private
statement in a module. It looks like the variables, functions and subroutines
which are declared private in module are exposed to the outside world when this
module is used the use statement. 

The attachment tarball is a relative simple example of the bug. In this error I
got the error 'is already declared in this scoping unit' error together with
the message 'It is use-associated with <variable> in module <module>'. I tried
to rename the <variable> in the use statement. In that case the front-end works
fine but gfortran complains that it can not find the <variable>, which I
understand since it is a private variable in used <module>.

Best regards,
   Jan-Willem

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20210103/76545251/attachment-0001.html>