public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "orion at cora dot nwra.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/60810] New: [4.9 Regression] list directed io from array results in end of file Date: Thu, 10 Apr 2014 17:31:00 -0000 [thread overview] Message-ID: <bug-60810-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60810 Bug ID: 60810 Summary: [4.9 Regression] list directed io from array results in end of file Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: orion at cora dot nwra.com This program: program readstrlist character(len=80), dimension(2) :: ver integer :: a, b, c ver(1) = '285 383' ver(2) = '985' read( ver, *) a, b, c write ( *, *) a, b, c end Outputs: At line 8 of file readstrlist.f90 Fortran runtime error: End of file with: Using built-in specs. COLLECT_GCC=gfortran COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/4.9.0/lto-wrapper Target: x86_64-redhat-linux Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --enable-multilib --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-gnu-unique-object --enable-linker-build-id --with-linker-hash-style=gnu --enable-languages=c,c++,objc,obj-c++,java,fortran,ada,go,lto --enable-plugin --enable-initfini-array --enable-java-awt=gtk --disable-dssi --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre --enable-libgcj-multifile --enable-java-maintainer-mode --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --disable-libjava-multilib --with-isl=/builddir/build/BUILD/gcc-4.9.0-20140409/obj-x86_64-redhat-linux/isl-install --with-cloog=/builddir/build/BUILD/gcc-4.9.0-20140409/obj-x86_64-redhat-linux/cloog-install --enable-gnu-indirect-function --with-tune=generic --with-arch_32=i686 --build=x86_64-redhat-linux Thread model: posix gcc version 4.9.0 20140409 (Red Hat 4.9.0-0.9) (GCC) works with 4.8.2 and earlier and ifort version 14.0.2.
next reply other threads:[~2014-04-10 17:31 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-04-10 17:31 orion at cora dot nwra.com [this message] 2014-04-11 1:55 ` [Bug fortran/60810] " jvdelisle at gcc dot gnu.org 2014-04-11 5:35 ` jakub at gcc dot gnu.org 2014-04-11 9:08 ` rguenth at gcc dot gnu.org 2014-04-11 9:12 ` [Bug fortran/60810] [4.7/4.8/4.9 " jakub at gcc dot gnu.org 2014-04-11 9:12 ` jakub at gcc dot gnu.org 2014-04-11 19:41 ` [Bug fortran/60810] [4.7/4.8/4.9/4.10 " jvdelisle at gcc dot gnu.org 2014-04-11 20:18 ` jvdelisle at gcc dot gnu.org 2014-04-11 21:54 ` jvdelisle at gcc dot gnu.org 2014-04-12 0:05 ` jvdelisle at gcc dot gnu.org 2014-04-12 0:06 ` jvdelisle at gcc dot gnu.org 2014-04-12 18:42 ` jvdelisle at gcc dot gnu.org 2014-04-12 18:51 ` jvdelisle at gcc dot gnu.org 2014-04-13 2:10 ` jvdelisle at gcc dot gnu.org 2014-04-16 15:20 ` orion at cora dot nwra.com 2014-04-29 3:14 ` jvdelisle at gcc dot gnu.org 2014-04-29 3:15 ` 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=bug-60810-4@http.gcc.gnu.org/bugzilla/ \ --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).