[Bug fortran/92065] [8/9/10/11 Regression] internal compiler error: in expand_expr_real_1

[sgk at troutmask dot apl.washington.edu]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92065

--- Comment #9 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Sat, Dec 19, 2020 at 11:35:24PM +0000, gtoth at umich dot edu wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92065
> 
> 
> 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.
> 

Apparently, you missed the word "volunteer".  How much did you
(and others) pay in ifort and nagfor licenses and support 
contracts?  No one is willing to pay for general maintianence
of gfortran.  At best, you may find someone willing to pay for
a specific feature (e.g., ORNL's support for work on openacc).
I've fixed 100s of bugs and implemented some new features for
gfortran.  Many of my fixes are for bugs that affected my own
Fortran code.  Some are for bugs in areas of the compiler I
know well.  I've also reviewed 100s of patches by others.
I do not use the OOP features of Fortran, so I have very little
knowledge about its implementation details.  So, your SOL 
if you're waiting for me to fix this bug.

Rants, like yours here, are one of two reasons why I've
stopped contributing to gfortran.  I will no longer review
patches, and if I submit a patch, it will be to fix a bug
affecting my code.