This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: The future of gfortran maintenance.
Hi!
Thanks a lot for pointing that to me, I hadn't even noticed it was
labelled as "ice-on-invalid-code".
I believe the orginal code to be valid: several compilers happily sail
through it, even the Lahey one at its pickiest find nothing to report
about it! This part (of the original code) is unfortunately very
convoluted (...), and I wasn't able to reduce it, FX was kind enough to
do it for me, but it could that I missed something: could you point out
to me the invalid bit please? If it's wrong in the original code, then
that's the end of the story (but I find it hard to believe)...
Thanks!
Philippe
PS: the error I currently get:
/USER/Alpha/Sim/SimF/philippe/MICRESS/MICRESS_GFortran/MICRESS/modules/MODULE_SPRACHE.f90:
In function 'ctn_error_interception':
/USER/Alpha/Sim/SimF/philippe/MICRESS/MICRESS_GFortran/MICRESS/modules/MODULE_SPRACHE.f90:342:
internal compiler error: in gfc_conv_variable, at
fortran/trans-expr.c:354
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
PPS: the version is used for that: GNU Fortran 95 (GCC) 4.2.0 20060206
(experimental)
Tobias.Schlueter@Physik.Uni-Muenchen.DE wrote:
>
> Quoting Philippe Schaffnit <P.Schaffnit@access.rwth-aachen.de>:
> > Please do not let PR 21877 fall through the cracks... It is still very
> > much there (well, as of last thursday)
>
> I suppose you're more worried about the ice-on-valid-code bug 19546 than the
> ice-on-invalid-code bug 21877?
>
> - Tobi