public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "blime at cox dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/20235] New: Gfortran internal read error Date: Sun, 27 Feb 2005 22:29:00 -0000 [thread overview] Message-ID: <20050227171349.20235.blime@cox.net> (raw) /sodsim/local/gcc-4.0-20050220#>gcc -v Using built-in specs. Target: sparc-sun-solaris2.8 Configured with: ../configure --enable-languages=c,f95 Thread model: posix gcc version 4.0.0 20050220 (experimental) Build with no problems. This little test program was created as a result of a runtime error on a large program used to test gfortran. G77 does not have this problem. ************************************************************************ program ntst character*16 bufld character*142 line open (10,file='bumsls',status='old') 32 read (10,'(a)',end=33) line if (line(1:1) .eq. '.') goto 32 write(*,*) 'write values on the line ',line write(*,*) read (line,79) bufld,budelt 79 format (t43,a16,t61,f8.0) write(*,*) 'write 2 values from the line ',bufld,budelt write(*,*) 33 continue end ************************************************************************ At line 14 of file ntst.f Fortran runtime error: Bad value during floating point read -- Summary: Gfortran internal read error Product: gcc Version: 4.0.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: blime at cox dot net CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20235
next reply other threads:[~2005-02-27 17:14 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-02-27 22:29 blime at cox dot net [this message] 2005-02-28 1:09 ` [Bug fortran/20235] " blime at cox dot net 2005-02-28 2:33 ` tobi at gcc dot gnu dot org 2005-06-01 9:45 ` fxcoudert 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=20050227171349.20235.blime@cox.net \ --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).