public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Thomas dot Koenig at online dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/18398] Formatted I/O problems
Date: Wed, 05 Jan 2005 08:34:00 -0000 [thread overview]
Message-ID: <20050105083356.9667.qmail@sourceware.org> (raw)
In-Reply-To: <20041109140117.18398.sfilippone@uniroma2.it>
------- Additional Comments From Thomas dot Koenig at online dot de 2005-01-05 08:33 -------
A testcase with character variables:
$ gfortran cline
$ cat cline.f
character*2 c1,c2
open(7)
write (7,'(A1)') 'a','b','c'
rewind(7)
read(7,'(A2)') c1,c2
print *,c1,c2
if (c2 .ne. 'b ') call abort
end
$ gfortran cline.f
$ ./a.out
a c
Aborted
$ g77 cline.f
$ ./a.out
a b
I think this bug can be summed up as:
"Input Format longer than line length causes following record to be skipped".
This bug may be the reason for the I/O related LAPACK failures.
In the driver programs, for example cchkaa.f at line 314, there's the line
READ( NIN, FMT = '(A72)', END = 140 )ALINE
If the input line in question is shorter than 72 characters, this bug
will cause the next line to be skipped, with - presumably - bad consequences.
--
What |Removed |Added
----------------------------------------------------------------------------
CC| |Thomas dot Koenig at online
| |dot de
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18398
next prev parent reply other threads:[~2005-01-05 8:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-09 14:01 [Bug libfortran/18398] New: " sfilippone at uniroma2 dot it
2004-11-09 14:03 ` [Bug libfortran/18398] " sfilippone at uniroma2 dot it
2004-11-09 14:03 ` sfilippone at uniroma2 dot it
2004-11-26 14:34 ` bdavis at gcc dot gnu dot org
2004-11-27 15:34 ` bdavis at gcc dot gnu dot org
2005-01-04 22:20 ` Thomas dot Koenig at online dot de
2005-01-04 22:31 ` Thomas dot Koenig at online dot de
2005-01-05 8:34 ` Thomas dot Koenig at online dot de [this message]
2005-01-06 6:13 ` bdavis at gcc dot gnu dot org
2005-01-06 14:41 ` tobi at gcc dot gnu dot org
2005-01-07 3:25 ` cvs-commit at gcc dot gnu dot org
2005-01-07 14:01 ` 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=20050105083356.9667.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).