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.