From: Jerry DeLisle <jvdelisle@charter.net>
To: Janne Blomqvist <blomqvist.janne@gmail.com>,
fortran@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH, libfortran] PR 48587 Newunit allocator
Date: Thu, 13 Oct 2016 17:16:00 -0000 [thread overview]
Message-ID: <0dfb6517-edd2-7340-2f2d-3519b98b6ebb@charter.net> (raw)
In-Reply-To: <1476371788-6740-1-git-send-email-blomqvist.janne@gmail.com>
On 10/13/2016 08:16 AM, Janne Blomqvist wrote:
> Currently GFortran newer reuses unit numbers allocated with NEWUNIT=,
> instead having a simple counter that is decremented each time such a
> unit is opened.
I am going to have to study this a bit. After I added the newunit stack, the
units are reused, Need to see how this plays with internal units, and
recursive, and dtio.
Jerry
next prev parent reply other threads:[~2016-10-13 17:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 15:16 Janne Blomqvist
2016-10-13 17:16 ` Jerry DeLisle [this message]
2016-10-13 20:08 ` Jerry DeLisle
2016-10-14 17:02 ` Bernhard Reutner-Fischer
2016-10-14 20:41 ` Janne Blomqvist
2016-10-15 1:15 ` Bernhard Reutner-Fischer
2016-10-14 21:48 ` Janne Blomqvist
2016-10-18 9:10 ` Steven Bosscher
2016-10-18 10:14 ` Janne Blomqvist
2016-10-13 21:00 Dominique d'Humières
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0dfb6517-edd2-7340-2f2d-3519b98b6ebb@charter.net \
--to=jvdelisle@charter.net \
--cc=blomqvist.janne@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).