https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108056
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to sandra from comment #7)
If gcc 11 had a bug that
> caused it to do that incorrectly, is it necessary to retain ABI
> compatibility by continuing to reproduce the bug in newer versions of
> libgfortran? Maybe we should just remove the functions that are allegedly
> there for compatibility so that users will get a link error instead?
No, certainly not. As long as libgfortran.so keeps its SONAME
(libgfortran.so.5 right now), it should remain backwards compatible
(libgfortran.so.5 from newer gcc should handle programs compiled by older gcc
as long as the programs were valid).
