public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mikael at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/58007] [OOP] ICE in free_pi_tree(): Unresolved fixup - resolve_fixups does not fixup component of __class_bsr_Bsr_matrix Date: Tue, 13 Aug 2013 11:47:00 -0000 [thread overview] Message-ID: <bug-58007-4-9yE4YWeVCF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-58007-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58007 Mikael Morin <mikael at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mikael at gcc dot gnu.org --- Comment #5 from Mikael Morin <mikael at gcc dot gnu.org> --- I suppose the following is happening (based on Janus' test): - At the time bsr is use-associated we see references to matrix::sparse_matrix, but as the type has already been loaded, we redirect references to matrix::sparse_matrix to the one already loaded. See read_module, the code that comes after the comment: /* See if the symbol has already been loaded by a previous module. If so, we reference the existing symbol and prevent it from being loaded again. This should not happen if the symbol being read is an index for an assumed shape dummy array (ns != 1). */ - Normally, mio_component (called from mio_component_list, from mio_symbol) associates a component pointer to the corresponding pointer id so that it can be referenced in expressions for example. As the type is not loaded from file (see above) the association isn't done either. - get_neighbors contains an expression (in the result's array spec) referencing max_degree, one of matrix::sparse_matrix's components. Because of the above, the reference is not associated with the corresponding component pointer, and it leads to the internal error.
next prev parent reply other threads:[~2013-08-13 11:47 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-07-28 4:02 [Bug fortran/58007] New: ICE -- free_pi_tree(): Unresolved fixup, depends on order of module inclusion shapero at uw dot edu 2013-07-28 7:49 ` [Bug fortran/58007] " burnus at gcc dot gnu.org 2013-07-28 9:50 ` [Bug fortran/58007] ICE in free_pi_tree(): Unresolved fixup - resolve_fixups does not fixup component of __class_bsr_Bsr_matrix burnus at gcc dot gnu.org 2013-07-28 16:45 ` shapero at uw dot edu 2013-08-13 8:59 ` janus at gcc dot gnu.org 2013-08-13 11:47 ` mikael at gcc dot gnu.org [this message] 2013-08-14 16:19 ` [Bug fortran/58007] [OOP] " mikael at gcc dot gnu.org 2013-08-14 16:23 ` mikael at gcc dot gnu.org 2013-08-14 16:46 ` mikael at gcc dot gnu.org 2013-09-11 16:05 ` townsend at astro dot wisc.edu 2013-12-06 10:31 ` [Bug fortran/58007] [4.7/4.9 Regression] " janus at gcc dot gnu.org 2013-12-19 15:19 ` rguenth at gcc dot gnu.org 2013-12-19 15:31 ` rguenth at gcc dot gnu.org 2013-12-24 0:37 ` townsend at astro dot wisc.edu 2013-12-25 16:06 ` mikael at gcc dot gnu.org 2014-01-18 20:21 ` mikael at gcc dot gnu.org 2014-01-18 21:24 ` mikael at gcc dot gnu.org 2014-01-26 13:05 ` mikael at gcc dot gnu.org 2014-01-26 14:50 ` mikael at gcc dot gnu.org 2014-01-26 14:52 ` mikael at gcc dot gnu.org 2014-01-27 21:23 ` mikael at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-58007-4-9yE4YWeVCF@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).