https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102992
--- Comment #20 from Thomas Koenig <tkoenig at gcc dot gnu.org> --- (In reply to Iain Sandoe from comment #16) > (In reply to Thomas Koenig from comment #14) > NOTE: I have been discussing the non-running of mod_term_funcs with my > "downstream" and Apple folks. The consensus is that this is 99.99% likely > an unintentional bug that just happens not to show with clang-based > toolchains because they queue DTORs on atexit (as does GCC for C++). > > > I guess that could be put into main, after the call to __MAIN, instead. > > Well, unless there's a good reason to have it in a DTOR, it makes for a more > robust solution to call it directly (there are various other differences > that could occur in mixed code bases esp. c++ + fortran even without the > Darwin21.1 bug). There is always the reason of not breaking compatibility, a quick look at close_units() shows that it is not meant to be called twice, so combining both methods is likely to cause headaches. So, something for the next incompatible libgfortran update, maybe. Maybe flushing all units on program termination would be safer, but I am not sure we should put in a workaround for what appears to be a bug in the underlying system (hopefully soon to be fixed), especially since there seems to be a workaround in user code.
