public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/45129] I/O edit descriptors: Warn if the format field is too small for the E and F edit descriptor
Date: Thu, 29 Jul 2010 21:07:00 -0000 [thread overview]
Message-ID: <20100729210704.14177.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45129-13404@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from burnus at gcc dot gnu dot org 2010-07-29 21:07 -------
For completeness, the current patch has failures for for following test cases.
In particular:
- Reading - here, the d == 0 does not harm (e.g. fmt_bz_bn.f).
- FMT_G: Here, the the width check is wrong (e.g. transpose_reshape_r10.f90)
- For writing, for 1P it might be zero, cf. fmt_zero_digits.f90
Thus, the simple check does not make much sense. Probably, one should just
remove it and leave only warning part in - with a fix for Gw.d? For read, more
is possible - but I think the fields are small enough that one could still warn
- or should one restrict the warning to WRITE/PRINT - and not include
READ/FORMAT?
gfortran.dg/fmt_bz_bn.f
gfortran.dg/fmt_read_bz_bn.f90
gfortran.dg/fmt_zero_digits.f90
gfortran.dg/fmt_zero_precision.f90
gfortran.dg/io_constraints_4.f90
gfortran.dg/past_eor.f90
gfortran.dg/read_infnan_1.f90
gfortran.dg/transpose_reshape_r10.f90
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45129
next prev parent reply other threads:[~2010-07-29 21:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 13:52 [Bug fortran/45129] New: " burnus at gcc dot gnu dot org
2010-07-29 17:25 ` [Bug fortran/45129] " domob at gcc dot gnu dot org
2010-07-29 19:33 ` burnus at gcc dot gnu dot org
2010-07-29 21:07 ` burnus at gcc dot gnu dot org [this message]
2010-07-30 1:56 ` jvdelisle at gcc dot gnu dot org
[not found] <bug-45129-4@http.gcc.gnu.org/bugzilla/>
2010-11-16 14:52 ` burnus at gcc dot gnu.org
2011-01-17 21:14 ` jvdelisle at gcc dot gnu.org
2011-06-15 8:55 ` burnus at gcc dot gnu.org
2013-02-15 7:38 ` burnus at gcc dot gnu.org
2014-03-30 18:09 ` dominiq at lps dot ens.fr
2023-10-13 20:30 ` jvdelisle at gcc dot gnu.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=20100729210704.14177.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).