https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61933
Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #10 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> --- It occurs to me another possible interpretation of what a unit existence might be. Behind the scenes when opening a unit with no filename we create a file named for example fort.10. That file name is processor dependent and the user should not know what that filename is. (we know by convention of course) I wonder now whether we should define unit existence to be whether or not the corresponding file (or device, or whatever it is....) exists on the system. This starts to make some sense when you think about it and could assist a user from inadvertently overwriting some existing data. I am going to reopen this for further discussion. I do agree with your issue.