[Bug libfortran/48587] Avoid exhausting unit number with NEWUNIT=

2016-10-15 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48587 Janne Blomqvist changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug libfortran/48587] Avoid exhausting unit number with NEWUNIT=

2016-10-15 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48587 --- Comment #10 from Janne Blomqvist --- Author: jb Date: Sun Oct 16 06:28:15 2016 New Revision: 241211 URL: https://gcc.gnu.org/viewcvs?rev=241211&root=gcc&view=rev Log: PR 48587 Newunit allocator, cleanup Improve error message, and remove a r

[Bug libfortran/48587] Avoid exhausting unit number with NEWUNIT=

2016-10-15 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48587 --- Comment #9 from Janne Blomqvist --- Author: jb Date: Sat Oct 15 13:15:26 2016 New Revision: 241200 URL: https://gcc.gnu.org/viewcvs?rev=241200&root=gcc&view=rev Log: PR 48587 Newunit allocator 2016-10-15 Janne Blomqvist PR libfo

[Bug libfortran/48587] Avoid exhausting unit number with NEWUNIT=

2016-10-15 Thread jb at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48587 --- Comment #8 from Janne Blomqvist --- Author: jb Date: Sat Oct 15 13:14:15 2016 New Revision: 241199 URL: https://gcc.gnu.org/viewcvs?rev=241199&root=gcc&view=rev Log: PR 48587 Newunit allocator Currently GFortran newer reuses unit numbers al

[Bug libfortran/48587] Avoid exhausting unit number with NEWUNIT=

2014-03-03 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48587 Janne Blomqvist changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |jb at gcc dot gnu.org --- Commen

[Bug libfortran/48587] Avoid exhausting unit number with NEWUNIT=

2011-04-19 Thread fxcoudert at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48587 Francois-Xavier Coudert changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug libfortran/48587] Avoid exhausting unit number with NEWUNIT=

2011-04-15 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48587 --- Comment #5 from Janne Blomqvist 2011-04-15 09:13:14 UTC --- Reading the standard, my simple suggestion in #1 will not actually work. One reason is that the NEWUNIT value may not be -1; with my approach this is possible if one first closes fd

[Bug libfortran/48587] Avoid exhausting unit number with NEWUNIT=

2011-04-14 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48587 --- Comment #4 from Janne Blomqvist 2011-04-14 08:12:33 UTC --- (In reply to comment #3) > I suppose one could put an OPEN .. CLOSE in a DO LOOP and see what happens > now. With gfortran 4.4.3 on Linux 2.6.32, /tmp on ext4, single SATA disk, an

[Bug libfortran/48587] Avoid exhausting unit number with NEWUNIT=

2011-04-13 Thread jvdelisle at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48587 Jerry DeLisle changed: What|Removed |Added CC||jvdelisle at gcc dot |

[Bug libfortran/48587] Avoid exhausting unit number with NEWUNIT=

2011-04-13 Thread jb at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48587 --- Comment #2 from Janne Blomqvist 2011-04-13 10:46:42 UTC --- (In reply to comment #1) > There is a problem with reusing numbers - it is probably only a small one - > but > it might be larger than the problem of running out of unit IDs: > > T

[Bug libfortran/48587] Avoid exhausting unit number with NEWUNIT=

2011-04-13 Thread burnus at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48587 Tobias Burnus changed: What|Removed |Added CC||burnus at gcc dot gnu.org --- Comment #1