http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45827

           Summary: mio_component_ref(): Component not found when mixing
                    f90 and f03 in large projects
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassig...@gcc.gnu.org
        ReportedBy: boschm...@tp1.physik.uni-siegen.de


Created attachment 21911
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=21911
The sample source code of this bug report

common.f03:27.22:

  use arguments_module
                      1
Interner Fehler bei (1):
mio_component_ref(): Component not found

GNU Fortran (GCC) 4.6.0 20100921 (experimental)


Hi all!

First of all, I'm sorry about the bad sample code for this bug. It is attached
to the report as "gccbug.tar.gz". This bug has bothered me for a while and I
never was able to isolate it. The error message comes and goes when I update to
the latest revision of gfortran and appears in a part of my project, when I
edit a completely different part. Now it showed up in a module with few
dependencies to other modules. It is the smallest collection of modules so far,
that show this bug. I can repair it, when

* I rename all files to *.f03. Usually, *.f90 files are mixed with *.f03 in my
project. Maybe this is not supposed to work, but the compiler should give a
better error message then.

* I add an use statement for all modules that are used by the used modules and
put them into proper order, such that no module depends to a module that is
"used" further down. That is what I've done until now, because I didn't knew
the first fact till this day. But in 4.6.0 20100921, even this has failed.

* I remove symbols somewhere. Obviously, the bug needs a certain complexity to
show up. That's why I cannot give you a smaller sample code.

* I use the actual GNU Fortran (GCC) 4.6.0 20100928. But it already happened,
that the bug disappeared and appeared again.

Best regards,
Hans Boschmann

Reply via email to