public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/20257] Fortran runtime error: End of record occurs when writing large arrays Date: Sun, 23 Apr 2006 02:05:00 -0000 [thread overview] Message-ID: <20060423020509.15548.qmail@sourceware.org> (raw) In-Reply-To: <bug-20257-10182@http.gcc.gnu.org/bugzilla/> ------- Comment #10 from jvdelisle at gcc dot gnu dot org 2006-04-23 02:05 ------- Subject: Bug 20257 Author: jvdelisle Date: Sun Apr 23 02:04:58 2006 New Revision: 113190 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=113190 Log: 2006-04-22 Jerry DeLisle <jvdelisle@gcc.gnu.org> PR libgfortran/20257 * io/io.h: Add prototypes for get_internal_unit and free_internal_unit. * io/unit.c (get_internal_unit): Initialize unit number, not zero. (free_internal_unit): New function to consolidate freeing memory. (get_unit): Initialize internal_unit_desc to NULL when unit is external. * io/unix.c (mem_close): Check for not NULL before freeing memory. * io/transfer.c (read_block): Reset bytes_left and skip error if unit is preconnected and default record length is reached. (read_block_direct): Ditto. (write_block): Ditto. (write_buf): Ditto. (data_transfer_init): Only flush if not internal unit. (finalize_transfer): Ditto and delete code to free memory used by internal units. (st_read_done): Use new function - free_internal_unit. (st_write_done): Use new function - free_internal unit. Modified: trunk/libgfortran/ChangeLog trunk/libgfortran/io/io.h trunk/libgfortran/io/transfer.c trunk/libgfortran/io/unit.c trunk/libgfortran/io/unix.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20257
next prev parent reply other threads:[~2006-04-23 2:05 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-20257-10182@http.gcc.gnu.org/bugzilla/> 2006-01-25 7:30 ` jvdelisle at gcc dot gnu dot org 2006-01-25 9:32 ` fxcoudert at gcc dot gnu dot org 2006-04-15 7:15 ` jvdelisle at gcc dot gnu dot org 2006-04-20 23:20 ` patchapp at dberlin dot org 2006-04-23 2:05 ` jvdelisle at gcc dot gnu dot org [this message] 2006-04-29 4:27 ` jvdelisle at gcc dot gnu dot org 2006-04-29 5:47 ` jvdelisle at gcc dot gnu dot org 2005-03-01 2:50 [Bug fortran/20257] New: " kamaraju at gmail dot com 2005-03-01 13:59 ` [Bug libfortran/20257] " pinskia at gcc dot gnu dot org 2005-03-02 9:35 ` coudert at clipper dot ens dot fr 2005-03-03 10:34 ` coudert at clipper dot ens dot fr 2005-03-03 13:08 ` coudert at clipper dot ens dot fr 2005-03-18 7:11 ` fxcoudert at gcc dot gnu dot org 2005-09-25 20:29 ` pinskia at gcc dot gnu dot 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=20060423020509.15548.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: linkBe 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).