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] [4.7/4.9 Regression] [OOP] ICE in free_pi_tree(): Unresolved fixup - resolve_fixups does not fixup component of __class_bsr_Bsr_matrix
Date: Sun, 26 Jan 2014 14:50:00 -0000 [thread overview]
Message-ID: <bug-58007-4-84eYUOmmzX@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
--- Comment #18 from Mikael Morin <mikael at gcc dot gnu.org> ---
Author: mikael
Date: Sun Jan 26 14:49:47 2014
New Revision: 207119
URL: http://gcc.gnu.org/viewcvs?rev=207119&root=gcc&view=rev
Log:
fortran/
PR fortran/58007
* module.c (fp2, find_pointer2): Remove.
(mio_component_ref): Don't forcedfully set the containing derived type
symbol for loading. Remove unused argument.
(mio_ref): Update caller
(skip_list): New argument nest_level. Initialize level with the new
argument.
(read_module): Add forced pointer components association for derived
type symbols.
testsuite/
PR fortran/58007
* gfortran.dg/unresolved_fixup_1.f90: New test.
* gfortran.dg/unresolved_fixup_2.f90: New test.
Added:
branches/gcc-4_7-branch/gcc/testsuite/gfortran.dg/unresolved_fixup_1.f90
branches/gcc-4_7-branch/gcc/testsuite/gfortran.dg/unresolved_fixup_2.f90
Modified:
branches/gcc-4_7-branch/gcc/fortran/ChangeLog
branches/gcc-4_7-branch/gcc/fortran/module.c
branches/gcc-4_7-branch/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2014-01-26 14:50 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 ` [Bug fortran/58007] [OOP] " mikael at gcc dot gnu.org
2013-08-14 16:19 ` 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 [this message]
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-84eYUOmmzX@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: link
Be 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).