public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/34565] internal write to string array fails Date: Thu, 03 Jan 2008 20:11:00 -0000 [thread overview] Message-ID: <20080103195052.19878.qmail@sourceware.org> (raw) In-Reply-To: <bug-34565-13404@http.gcc.gnu.org/bugzilla/> ------- Comment #8 from tkoenig at gcc dot gnu dot org 2008-01-03 19:50 ------- Subject: Bug 34565 Author: tkoenig Date: Thu Jan 3 19:49:38 2008 New Revision: 131305 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=131305 Log: 2008-01-03 Thomas Koenig <tkoenig@gcc.gnu.org> PR libfortran/34565 * io/io.h: Adjust protoypes for open_internal(), next_array_record() and init_loop_spec(). * io/list_read.c (next_char): Use argument "finished" of next_array_record to check for end on internal file. * io/unit.c: Calculate the offset for an array internal file and supply this informatin to open_internal(). * io/unix.c (open_internal): Set the offset for the internal file on open. * io/transfer.c (init_loop_spec): Calculate the starting record in case of negative strides. Return size of 0 for an empty array. (next_array_record): Use an extra flag to signal that the array is finished. (next_record_r): Use the new flag to next_array_record(). (next_record_w): Likewise. 2008-01-03 Thomas Koenig <tkoenig@gcc.gnu.org> PR libfortran/34565 * gfortran.dg/internal_readwrite_1.f90: New test. * gfortran.dg/internal_readwrite_2.f90: New test. Added: trunk/gcc/testsuite/gfortran.dg/internal_readwrite_1.f90 trunk/gcc/testsuite/gfortran.dg/internal_readwrite_2.f90 Modified: trunk/gcc/testsuite/ChangeLog trunk/libgfortran/ChangeLog trunk/libgfortran/io/io.h trunk/libgfortran/io/list_read.c trunk/libgfortran/io/transfer.c trunk/libgfortran/io/unit.c trunk/libgfortran/io/unix.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34565
next prev parent reply other threads:[~2008-01-03 19:51 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-12-23 11:38 [Bug fortran/34565] New: " burnus at gcc dot gnu dot org 2007-12-23 17:03 ` [Bug fortran/34565] " jvdelisle at gcc dot gnu dot org 2007-12-26 14:22 ` tkoenig at gcc dot gnu dot org 2007-12-27 15:07 ` tkoenig at gcc dot gnu dot org 2007-12-27 15:36 ` tkoenig at gcc dot gnu dot org 2007-12-28 1:00 ` jvdelisle at gcc dot gnu dot org 2007-12-28 13:16 ` tkoenig at gcc dot gnu dot org 2007-12-28 15:39 ` jvdelisle at gcc dot gnu dot org 2008-01-03 20:11 ` tkoenig at gcc dot gnu dot org [this message] 2008-01-03 20:12 ` tkoenig 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=20080103195052.19878.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).