public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/60956] [4.8/4.9/5 Regression] error reading (and writing) large text files in gfortran
Date: Fri, 06 Feb 2015 11:07:00 -0000	[thread overview]
Message-ID: <bug-60956-4-EWxc7pCaJh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60956-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60956

Tobias Burnus <burnus at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |burnus at gcc dot gnu.org

--- Comment #5 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to Jerry DeLisle from comment #3)
> I took a closer look at this one. The error I am getting is running out of
> allocatable space in realloc used in fbuf.c (fbuf_alloc).  We are allocating
> one byte at a time, and just keep trying to douple the buffer when its not
> big enough.
> 
> I think we need to check for some max buffer size and when we approach it,
> flush the fbuf and continue.

I think we cannot completely get rid of buffering a complete record - if we do
formatted I/O (contrary to list-directed I/O and unformatted). The problem is
that the format can contain T, TL and TR.

However, the test case only contains list-directed I/O, which doesn't require
to cache the whole record.  [For formatted, one could check the format
statement - but there could be some performance trade off.]


  parent reply	other threads:[~2015-02-06 11:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-24 20:16 [Bug fortran/60956] New: " awrichar at gmail dot com
2015-02-06  4:48 ` [Bug fortran/60956] " jvdelisle at gcc dot gnu.org
2015-02-06  6:51 ` [Bug fortran/60956] [4.8/4.9/5 Regression] " tkoenig at gcc dot gnu.org
2015-02-06 11:07 ` burnus at gcc dot gnu.org [this message]
2015-02-06 14:22 ` jvdelisle at gcc dot gnu.org
2015-02-06 15:00 ` jvdelisle at gcc dot gnu.org
2015-02-07  2:20 ` jvdelisle at gcc dot gnu.org
2015-02-07 15:13 ` jvdelisle at gcc dot gnu.org
2015-02-07 15:24 ` jakub at gcc dot gnu.org
2015-03-23  1:32 ` jvdelisle at gcc dot gnu.org
2015-03-23  4:55 ` jvdelisle at gcc dot gnu.org
2015-03-23  5:47 ` 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=bug-60956-4-EWxc7pCaJh@http.gcc.gnu.org/bugzilla/ \
    --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).