Created attachment 23864 [details] reduced program fortran code that triggers the internal error I have reduced a fortran program to the attached test case that triggers the following internal error: $ gfortran mio_component_ref_error.f90 mio_component_ref_error.f90:45.41: use elliptical_elements, only : line 1 Internal Error at (1): mio_component_ref(): Component not found This happens using gfortran 4.5.1, 4.6.0, and the trunk build from yesterday (4.7). The error goes away if you copy the line() function from the elliptical_elements module into the the solution_mod module and comment out the use statement on line 45. Maybe this bug is related to bug 47601? I am experiencing this problem in 64-bit Ubuntu Linux. -- I don't know if the following tidbit helps, but while I was cutting the program down to this test case, I briefly experienced the following different error at the same location when I eliminated some of the extends() dependencies of one type on another in the type_definitions module. I can't seem to reproduce this different error anymore, though. gfortran -c -o solution.o solution.f90 solution.f90:10.41: use elliptical_elements, only : line 1 Internal Error at (1): free_pi_tree(): Unresolved fixup
This pr looks like a duplicate of pr47601.
(In reply to comment #0) > I don't know if the following tidbit helps, but while I was cutting the program > down to this test case, I briefly experienced the following different error at > the same location when I eliminated some of the extends() dependencies of one > type on another in the type_definitions module. I can't seem to reproduce this > different error anymore, though. > > gfortran -c -o solution.o solution.f90 > solution.f90:10.41: > > use elliptical_elements, only : line > 1 > Internal Error at (1): > free_pi_tree(): Unresolved fixup This is PR47546, which was closed after the error reported vanished. Can you reopen it and provide a case triggering it if you can reproduce again? (In reply to comment #1) > This pr looks like a duplicate of pr47601. Indeed, and the testcase matches the same pattern (use-associated extended derived-type component needed in function interface). *** This bug has been marked as a duplicate of bug 47601 ***