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: Sun, 10 Jul 2005 01:59:00 -0000 [thread overview]
Message-ID: <20050709234037.23687.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-07-09 23:40 -------
Subject: Bug 21875
CVSROOT: /cvs/gcc
Module name: gcc
Changes by: jvdelisle@gcc.gnu.org 2005-07-09 23:40:32
Modified files:
libgfortran : ChangeLog
libgfortran/io : read.c
Added files:
gcc/testsuite/gfortran.dg: fmt_read_bz_bn.f90
Log message:
2005-07-09 Jerry DeLisle <jvdelisle@verizon.net>
PR libfortran/21875 (FM111.f)
* io/read.c (next_char): Return a ' ' character when BLANK_ZERO or
BLANK_NULL are active.
(read_decimal): Interpret ' ' character correctly for BZ or BN.
(read_radix): Interpret ' ' character correctly for BZ or BN.
(read_f): Interpret ' ' character correctly for BZ or BN.
* gfortran.dg/test (fmt_read_bz_bn.f90): New test case.
Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/ChangeLog.diff?cvsroot=gcc&r1=1.259&r2=1.260
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/io/read.c.diff?cvsroot=gcc&r1=1.12&r2=1.13
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/gfortran.dg/fmt_read_bz_bn.f90.diff?cvsroot=gcc&r1=NONE&r2=1.1
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21875
next prev parent reply other threads:[~2005-07-09 23:40 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 [this message]
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
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=20050709234037.23687.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: 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).