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/15750] IOLENGTH form of INQUIRE statement not implemented Date: Tue, 22 Jun 2004 00:44:00 -0000 [thread overview] Message-ID: <20040622004409.1859.qmail@sourceware.org> (raw) In-Reply-To: <20040531143638.15750.jblomqvi@cc.hut.fi> ------- Additional Comments From cvs-commit at gcc dot gnu dot org 2004-06-22 00:44 ------- Subject: Bug 15750 CVSROOT: /cvs/gcc Module name: gcc Changes by: pbrook@gcc.gnu.org 2004-06-22 00:43:55 Modified files: gcc/fortran : ChangeLog io.c resolve.c trans-io.c gcc/testsuite : ChangeLog libgfortran : ChangeLog libgfortran/io : inquire.c io.h transfer.c Added files: gcc/testsuite/gfortran.fortran-torture/execute: iolength_1.f90 iolength_3.f90 Log message: PR fortran/15750 * io.c (gfc_match_inquire): Bugfix for iolength related stuff. (gfc_resolve_inquire): Resolve the iolength tag. Return SUCCESS at end of function if no failure has occured. * resolve.c (resolve_code): Resolve if iolength is encountered. * trans-io.c: (ioparm_iolength, iocall_iolength, iocall_iolength_done): New variables. (last_dt): Add IOLENGTH. (gfc_build_io_library_fndecls ): Set iolength related variables. (gfc_trans_iolength): Implement. (gfc_trans_dt_end): Treat iolength as a third form of data transfer. libgfortran/ PR fortran/15750 * inquire.c (st_inquire): Add comment * io.h (st_parameter): Add iolength. (st_iolength, st_iolength_done): Declare. * transfer.c (iolength_transfer, iolength_transfer_init, st_iolength, st_iolength_done): New functions. testsuite/ * gfortran.fortran-torture/execute/iolength_1.f90: New test. * gfortran.fortran-torture/execute/iolength_3.f90: New test. Patches: http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fortran/ChangeLog.diff?cvsroot=gcc&r1=1.81&r2=1.82 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fortran/io.c.diff?cvsroot=gcc&r1=1.8&r2=1.9 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fortran/resolve.c.diff?cvsroot=gcc&r1=1.7&r2=1.8 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/fortran/trans-io.c.diff?cvsroot=gcc&r1=1.5&r2=1.6 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/ChangeLog.diff?cvsroot=gcc&r1=1.3881&r2=1.3882 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/gfortran.fortran-torture/execute/iolength_1.f90.diff?cvsroot=gcc&r1=NONE&r2=1.1 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/gfortran.fortran-torture/execute/iolength_3.f90.diff?cvsroot=gcc&r1=NONE&r2=1.1 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/ChangeLog.diff?cvsroot=gcc&r1=1.39&r2=1.40 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/io/inquire.c.diff?cvsroot=gcc&r1=1.3&r2=1.4 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/io/io.h.diff?cvsroot=gcc&r1=1.5&r2=1.6 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/io/transfer.c.diff?cvsroot=gcc&r1=1.6&r2=1.7 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15750
next prev parent reply other threads:[~2004-06-22 0:44 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-05-31 22:59 [Bug fortran/15750] New: " jblomqvi at cc dot hut dot fi 2004-05-31 23:03 ` [Bug fortran/15750] [gfortran] " jblomqvi at cc dot hut dot fi 2004-05-31 23:21 ` pinskia at gcc dot gnu dot org 2004-06-20 15:24 ` [Bug fortran/15750] " pinskia at gcc dot gnu dot org 2004-06-20 15:27 ` jblomqvi at cc dot hut dot fi 2004-06-22 0:44 ` cvs-commit at gcc dot gnu dot org [this message] 2004-07-16 16:52 ` jblomqvi at cc dot hut dot fi 2004-08-29 17:04 ` tobi at gcc dot gnu dot org 2004-09-08 19:35 ` toon at moene dot indiv dot nluug dot nl 2004-09-09 23:08 ` jblomqvi at cc dot hut dot fi 2004-09-10 7:31 ` pinskia at gcc dot gnu dot org 2004-09-20 9:39 ` tobi at gcc dot gnu dot org 2004-09-20 9:40 ` tobi at gcc dot gnu dot org 2004-09-20 11:10 ` cvs-commit at gcc dot gnu dot org 2004-11-06 15:44 ` 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=20040622004409.1859.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).