https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106295
--- Comment #6 from ghlixo at gmail dot com --- One last comment about this issue. I maintain and distribute a Fortran subroutine package to users. In my experience, most of them are unaware that Fortran compilers evolve over time, and that the compiler used to build the subroutine package might not be the same version that they have installed. It seems that simple form of link-time version control might alert them to the problem, and avoid spurious problem reports. Would not a reference to a symbol in the run-time library dropped into compiled code when a library routine is used solve the problem? If the symbol definition changes when the library changes, then it would be impossible to link old code with an incompatible run-time library.
