This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug fortran/11125] New: internal compiler error: in lhd_incomplete_type_error, at langhooks.c:210


PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

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

           Summary: internal compiler error: in lhd_incomplete_type_error,
                    at langhooks.c:210
           Product: gcc
           Version: 3.3
            Status: UNCONFIRMED
          Severity: major
          Priority: P2
         Component: fortran
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: r.ems@gmx.net
                CC: gcc-bugs@gcc.gnu.org

SuSE Linux 8.2
rpm packages gcc-3.3-23 and gcc-g77-3.3-23.
"gcc --version": gcc (GCC) 3.3 20030226 (prerelease) (SuSE Linux)
"g77 --version": GNU Fortran (GCC) 3.3 20030226 (prerelease) (SuSE Linux)

"g77 -c -o ateig.o ateig.f" compiles without errors.
"g77 -c -ffortran-bounds-check -o ateig.o ateig.f" throws following error:
ateig.f: In subroutine `ateig':
ateig.f:145: internal compiler error: in lhd_incomplete_type_error, at
langhooks.c:210
Please submit a full bug report, with preprocessed source if appropriate.

I'm now compiling the final 3.3 release and will try again with it.
The same error is triggered by many different fortran programs.
On the examined 3 different cases, the errors triggers on assignment lines were
the assigned variable is defined as REAL var(1:*) or COMPLEX var(1:*).

The following code triggers the "bug?":

       subroutine test1(x)
       real x(1:*)
       i = 1
       x(i) = 0.0
       end

Thanks for help, Richard


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]