public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/37355] Request runtime preconnected buffer option for gfortran
Date: Tue, 13 Apr 2010 05:40:00 -0000	[thread overview]
Message-ID: <20100413054030.32230.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37355-9579@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from burnus at gcc dot gnu dot org  2010-04-13 05:40 -------
(In reply to comment #4)
> Looking at latest gfortran, we have raw_init and buf_init functions which set
> the style of I/O.  I think it would be relatively easy now to create a Gnu
> extension as an intrinsic procedure call that will force a flush on a unit

The question is whether it needs to be some easily accessible intrinsic
function or whether some __gfortran_set_* would be enough; cf.
http://gcc.gnu.org/onlinedocs/gfortran/Non_002dFortran-Main-Program.html

The latter, which just sets a variable would be also an option. Actually, one
could think of adding an item to _gfortran_set_options


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37355


  parent reply	other threads:[~2010-04-13  5:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-03 17:04 [Bug fortran/37355] New: " MMcVeigh at att dot net
2008-09-03 18:07 ` [Bug fortran/37355] " kargl at gcc dot gnu dot org
2008-09-08 18:31 ` tkoenig at gcc dot gnu dot org
2008-09-08 20:01 ` MMcVeigh at att dot net
2008-09-11 19:31 ` tkoenig at gcc dot gnu dot org
2010-04-13  4:10 ` jvdelisle at gcc dot gnu dot org
2010-04-13  5:40 ` burnus at gcc dot gnu dot org [this message]
     [not found] <bug-37355-4@http.gcc.gnu.org/bugzilla/>
2014-03-23  0:35 ` dominiq at lps dot ens.fr
2015-08-26 14:58 ` fxcoudert at gcc dot gnu.org
2015-08-30 21:48 ` dominiq at lps dot ens.fr
2015-08-31  2:41 ` jvdelisle at gcc dot gnu.org

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=20100413054030.32230.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).