https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92065
--- Comment #8 from Gabor <gtoth at umich dot edu> --- Dear HTH, Apparently this bug was reported years ago, and it was not fixed. There was no suggestion on how to avoid it either. I am not sure why gfortran is not supported by GNU, as it is used heavily in the computational physics community and gfortran is one of the compilers (the other is ifort) installed on supercomputers around the world. There are millions and millions of lines of code depending on Fortran and there are 10s of thousands of scientists and students using these codes. The only hope to adopt new (meaning beyond F77 and F90) features of Fortran by the community is to have compilers that can handle these new features. Why am I wasting time to write a nice piece of code (in this case a general interpolation routine that can handle any type of numbers) if in the end I get a compiler internal error. nagfor can handle it, ifort can handle it, gfortran cannot. And gfortran is one of the MAIN fortran compilers. So now I have to dumb down my code to the usual cut-and-paste style, repetition and so on, because I cannot use class(*). So I am frustrated. And maybe my frustration will motivate you to fix the problem. Thank you, Gabor > On Dec 19, 2020, at 6:17 PM, kargl at gcc dot gnu.org > <gcc-bugzi...@gcc.gnu.org> wrote: > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92065 > > kargl at gcc dot gnu.org changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |kargl at gcc dot gnu.org > > --- Comment #7 from kargl at gcc dot gnu.org --- > (In reply to Gabor from comment #6) >> I have the same problem with gfortran 9 and gfortran 10. After 17 years of >> Fortran 2003, one would hope to be able to use it. > > You forgot to attach your patch that fixes this issue. > > gfortran is mostly maintained and written by a dwindling number > of volunteers. Comments like your second sentence above is not > exactly motivating. > > HTH > > -- > You are receiving this mail because: > You are on the CC list for the bug.
