public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/48428] New: gfortran internal error
@ 2011-04-03 19:30 kristopher.kuhlman at gmail dot com
2011-04-04 9:37 ` [Bug fortran/48428] [OOP] ICE at mio_component_ref() / free_pi_tree() - module read issues? dominiq at lps dot ens.fr
2011-04-04 13:00 ` mikael at gcc dot gnu.org
0 siblings, 2 replies; 3+ messages in thread
From: kristopher.kuhlman at gmail dot com @ 2011-04-03 19:30 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48428
Summary: gfortran internal error
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: kristopher.kuhlman@gmail.com
Created attachment 23864
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=23864
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug fortran/48428] [OOP] ICE at mio_component_ref() / free_pi_tree() - module read issues?
2011-04-03 19:30 [Bug fortran/48428] New: gfortran internal error kristopher.kuhlman at gmail dot com
@ 2011-04-04 9:37 ` dominiq at lps dot ens.fr
2011-04-04 13:00 ` mikael at gcc dot gnu.org
1 sibling, 0 replies; 3+ messages in thread
From: dominiq at lps dot ens.fr @ 2011-04-04 9:37 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48428
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2011-04-04 09:36:03 UTC ---
This pr looks like a duplicate of pr47601.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug fortran/48428] [OOP] ICE at mio_component_ref() / free_pi_tree() - module read issues?
2011-04-03 19:30 [Bug fortran/48428] New: gfortran internal error kristopher.kuhlman at gmail dot com
2011-04-04 9:37 ` [Bug fortran/48428] [OOP] ICE at mio_component_ref() / free_pi_tree() - module read issues? dominiq at lps dot ens.fr
@ 2011-04-04 13:00 ` mikael at gcc dot gnu.org
1 sibling, 0 replies; 3+ messages in thread
From: mikael at gcc dot gnu.org @ 2011-04-04 13:00 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48428
Mikael Morin <mikael at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |mikael at gcc dot gnu.org
Resolution| |DUPLICATE
--- Comment #2 from Mikael Morin <mikael at gcc dot gnu.org> 2011-04-04 12:54:15 UTC ---
(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 ***
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2011-04-04 13:00 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-04-03 19:30 [Bug fortran/48428] New: gfortran internal error kristopher.kuhlman at gmail dot com
2011-04-04 9:37 ` [Bug fortran/48428] [OOP] ICE at mio_component_ref() / free_pi_tree() - module read issues? dominiq at lps dot ens.fr
2011-04-04 13:00 ` mikael at gcc dot gnu.org
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).