public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/21875] [meta-bug] NIST test suite failures Date: Wed, 14 Sep 2005 20:19:00 -0000 [thread overview] Message-ID: <20050914201912.5537.qmail@sourceware.org> (raw) In-Reply-To: <20050602054449.21875.fxcoudert@gcc.gnu.org> ------- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-09-14 20:19 ------- Subject: Bug 21875 CVSROOT: /cvs/gcc Module name: gcc Changes by: jvdelisle@gcc.gnu.org 2005-09-14 20:18:19 Modified files: libgfortran : ChangeLog libgfortran.h libgfortran/io : io.h transfer.c unit.c unix.c libgfortran/runtime: error.c Log message: 2005-09-14 Jerry DeLisle <jvdelisle@verizon.net PR fortran/21875 Internal Unit Array I/O, NIST * libgfortran.h: Add run time error code for array stride. * runtime/error.c (translate_error): Add error message for array stride. * io/io.h: Add array descriptor pointer to IOPARM structure. Add prtotypes for two new functions. * io/transfer.c (data_transfer_init): Removed initialization and moved to unit.c (get_unit) * io/transfer.c (next_record_r): Include internal unit read functionality. * io/transfer.c (next_record_w): Include internal unit write functionality, including padding of character array records. * io/unit.c (get_array_unit_len): New function to return the number of records in the character array 'file' from the array descriptor. * io/unit.c (get_unit): Gathered initialization code from init_data_transfer for internal units and added initialization of character array unit. * io/unit.c (is_array_io): New function to determine if internal unit is an array. * io/unix.c (mem_alloc_w_at): Add error checks for bad record length and end of file. Patches: http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/ChangeLog.diff?cvsroot=gcc&r1=1.303&r2=1.304 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/libgfortran.h.diff?cvsroot=gcc&r1=1.31&r2=1.32 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/io/io.h.diff?cvsroot=gcc&r1=1.30&r2=1.31 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/io/transfer.c.diff?cvsroot=gcc&r1=1.58&r2=1.59 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/io/unit.c.diff?cvsroot=gcc&r1=1.14&r2=1.15 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/io/unix.c.diff?cvsroot=gcc&r1=1.39&r2=1.40 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/runtime/error.c.diff?cvsroot=gcc&r1=1.14&r2=1.15 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21875
next prev parent reply other threads:[~2005-09-14 20:19 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-06-02 5:45 [Bug fortran/21875] New: [meta] " fxcoudert at gcc dot gnu dot org 2005-06-02 18:49 ` [Bug fortran/21875] [meta-bug] " pinskia at gcc dot gnu dot org 2005-06-16 23:04 ` fxcoudert at gcc dot gnu dot org 2005-06-17 16:25 ` fxcoudert at gcc dot gnu dot org 2005-07-08 2:01 ` jvdelisle at verizon dot net 2005-07-08 11:15 ` tobi at gcc dot gnu dot org 2005-07-10 1:59 ` cvs-commit at gcc dot gnu dot org 2005-07-11 1:12 ` cvs-commit at gcc dot gnu dot org 2005-07-13 1:37 ` janis at gcc dot gnu dot org 2005-07-13 3:03 ` pinskia at gcc dot gnu dot org 2005-07-13 17:09 ` janis at gcc dot gnu dot org 2005-07-20 6:06 ` jvdelisle at verizon dot net 2005-07-20 6:44 ` jvdelisle at verizon dot net 2005-07-20 15:55 ` janis at gcc dot gnu dot org 2005-07-22 14:36 ` cvs-commit at gcc dot gnu dot org 2005-07-24 0:05 ` cvs-commit at gcc dot gnu dot org 2005-07-24 0:56 ` cvs-commit at gcc dot gnu dot org 2005-09-04 6:11 ` jvdelisle at verizon dot net 2005-09-14 20:19 ` cvs-commit at gcc dot gnu dot org [this message] 2005-09-14 20:21 ` cvs-commit at gcc dot gnu dot org 2005-09-14 20:28 ` cvs-commit at gcc dot gnu dot org 2005-09-14 20:43 ` jvdelisle at verizon dot net 2005-09-16 3:24 ` jvdelisle 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=20050914201912.5537.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).