https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116701
--- Comment #2 from anlauf at gcc dot gnu.org --- (In reply to Hans-Peter Nilsson from comment #1) > The cause is that the unsigned_22 test (added in the named commit) leaves an > output file "fort.10", which is picked up by write_check3 which then calls > libgfortran raw_truncate. I guess the gfortran "unit-machinery" wants to > clear that file if it exists. > > Some option is needed to make the "fort.10" file name unique or something to > that effect in a way that it isn't picked up by write_check3. A dg- cleanup > function might do, perhaps one exists? A "git grep -w fort" in > testsuite/lib catches nothing though. Well observed. Can you test if adding a line close(10, status="delete") before the end program memain fixes the issue? If so, such a fix is pre-approved; you can also ask Thomas.
