Re: [patch, libgfortran, committed] PR89020

2019-01-27 Thread Jerry DeLisle
On 1/27/19 1:13 AM, Janne Blomqvist wrote: On Sat, Jan 26, 2019 at 10:42 PM Jerry DeLisle --- snip --- Checking remove() for an error is a good idea, although speculating why that happened might be confusing if the error happens for some other reason? Particularly so on POSIX systems, where

Re: [patch, libgfortran, committed] PR89020

2019-01-27 Thread Janne Blomqvist
On Sat, Jan 26, 2019 at 10:42 PM Jerry DeLisle wrote: > Committed as simple and obvious. (With a ChangeLog Bobble fixed) > > Regression tested on x86_64. > > Committed r268301 > M libgfortran/ChangeLog > M libgfortran/io/close.c > > Regards, > > Jerry > > 2019-01-26 J

[patch, libgfortran, committed] PR89020

2019-01-26 Thread Jerry DeLisle
Committed as simple and obvious. (With a ChangeLog Bobble fixed) Regression tested on x86_64. Committed r268301 M libgfortran/ChangeLog M libgfortran/io/close.c Regards, Jerry 2019-01-26 Jerry DeLisle PR libfortran/89020 * io/close.c (st_close):