public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "townsend at astro dot wisc.edu" <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: Wed, 11 Sep 2013 16:05:00 -0000 [thread overview]
Message-ID: <bug-58007-4-SMjHLQcMfp@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
Rich Townsend <townsend at astro dot wisc.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |townsend at astro dot wisc.edu
--- Comment #9 from Rich Townsend <townsend at astro dot wisc.edu> ---
(In reply to Mikael Morin from comment #8)
> Created attachment 30656 [details]
> tentative hack
>
> For some reason this patch fixes the internal error on comment #6, but not
> on comment #4.
I can conform that this patch works to fix the bug on trunk (rev. 202487)
running on OS X 10.7. Without the patch, the test case in #6 fails with the
usual unresolved fixup issue.
However, *with* Mikael's patch I'm no longer able to build the HDF5 libraries
(1.8.10-patch1). During compilation of the Fortran API, I get the following:
tH5L_F03.f90:125.6:
USE liter_cb_mod
1
Internal Error at (1):
free_pi_tree(): Unresolved fixup
make[2]: *** [tH5L_F03.o] Error 1
I configured thusly:
./configure --build=x86_64-apple-darwin11.4.2 --prefix=/Applications/mesasdk
--enable-fortran --enable-fortran2003
This has become a showstopper for me: I need Mikael's patch to fix unresolved
fixup issues with my own codes (with a similar trigger to the examples given
above), but I also need the HDF5 libraries for the codes. Unresolved fixups are
the #1 bug I've encountered with gfortran over the past year, yet due to their
very temperamental nature they're difficult to report and thus difficult to
make the gfortran developers sit up and take notice of.
So, I'd like to make a earnest plea to the devs: please get to the bottom of
this! I'm happy to work closely with you in coming up with test cases that
trigger the bug. But this really needs to be fixed; it basically kills gfortran
as a viable compiler.
next prev parent reply other threads:[~2013-09-11 16:05 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 [this message]
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-SMjHLQcMfp@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).