https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92065
--- Comment #13 from Thomas Koenig <tkoenig at gcc dot gnu.org> --- (In reply to Gabor from comment #10) > Good to know that gfortran has come to an end. It means, for example, that > i will not rely on the openacc implementation either. Or openmp5. Those two fields are actually seeing a lot of funded development right now, done by Mentor Graphics. OpenMP5 is not yet supported, but this is being worked on. As far as general development is concerned: Like Steve, I am one of the volunteers maintaining the compiler. You write that you're not a compiler writer; well, neither am I, in a professional sense. I am a chemical engineer who very occasionally uses Fortran for his day-time job. I contribute to gfortran mainly for three reasons: a) I like the language b) I like the intellectual challenge and c) I want to give something back to the open source community. People often think that you need to be an exceptionally good programmer to contribute to a compiler. I can testify from first-hand experience that this is not necessary, since I am absolutely certain that I am not exceptionally good :-) If you feel strongly that some bug should be fixed, there are several options available to you. You can convince the organization you work for to fund some bug-fixing. You can try to motivate people to fix this (negative motivation usually does not work), or you can try to fix it yourself. Although there is an entry barrier to doing things to the compiler, it is quite possible to find an entry to this, and it is always possible to ask for advice. A starting point is https://gcc.gnu.org/wiki/GFortranHacking . You will need a general-level knowledge of C for this (technically, the gfortran front end to gcc is written in C++, but it is very close to the common subset of C and C++).
