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/19678] New: DOS files don't work for list directed input Date: Fri, 28 Jan 2005 22:54:00 -0000 [thread overview] Message-ID: <20050128225425.19678.Thomas.Koenig@online.de> (raw) This time, the right bug report... CR-LF (the DOS convenction for text files) as record separators don't work for list-directed input. $ cat dosfile.f program main write (10,'(2A)') '1',achar(13) rewind(10) read(10,*) n print *,n end $ gfortran dosfile.f $ ./a.out At line 4 of file dosfile.f Fortran runtime error: Bad integer for item 1 in list input $ g77 dosfile.f $ ./a.out 1 $ od -c fort.10 0000000 1 \r \n 0000003 $ gfortran -v Using built-in specs. Configured with: ../gcc/configure --prefix=/home/ig25 --enable-languages=c,f95 Thread model: posix gcc version 4.0.0 20050127 (experimental) -- Summary: DOS files don't work for list directed input Product: gcc Version: 4.0.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: libfortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: Thomas dot Koenig at online dot de CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19678
next reply other threads:[~2005-01-28 22:54 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-01-28 22:54 Thomas dot Koenig at online dot de [this message] 2005-02-02 12:41 ` [Bug libfortran/19678] " paulthomas2 at wanadoo dot fr 2005-02-07 20:27 ` Thomas dot Koenig at online dot de 2005-02-24 16:21 ` coudert at clipper dot ens dot fr 2005-02-24 17:49 ` pinskia at gcc dot gnu dot org 2005-03-17 12:15 ` fxcoudert at gcc dot gnu dot org 2005-03-25 13:35 ` cvs-commit at gcc dot gnu dot org 2005-03-25 13:37 ` fxcoudert at gcc dot gnu dot org 2005-03-25 13:38 ` fxcoudert at gcc dot gnu dot org 2005-03-25 13:41 ` cvs-commit 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=20050128225425.19678.Thomas.Koenig@online.de \ --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).