public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/61049] New: [4.9/4.10 Regression] NIST test FM906 fails Date: Sat, 03 May 2014 21:00:00 -0000 [thread overview] Message-ID: <bug-61049-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61049 Bug ID: 61049 Summary: [4.9/4.10 Regression] NIST test FM906 fails Product: gcc Version: 4.10.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libfortran Assignee: unassigned at gcc dot gnu.org Reporter: dominiq at lps dot ens.fr CC: jvdelisle at gcc dot gnu.org The NIST test FM906 fails with gfortran 4.9.0 and trunk with At line 351 of file /Users/dominiq/Documents/Fortran/NISTtest/NIST/FM906.f (unit = 5, file = 'stdin') Fortran runtime error: Bad repeat count in item 5 of list input Reduced test character(len=30) :: buff = ", (2.0, 3.0),,6.0D0, 2*," DOUBLE PRECISION AVD, BVD, CVD, DVCORR COMPLEX AVC, BVC, CVC, ZVCORR read(buff, *) AVD, AVC, BVC, BVD, CVC, CVD end Revision r208599 is OK, r208775 is not. Likely r208629.
next reply other threads:[~2014-05-03 21:00 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-05-03 21:00 dominiq at lps dot ens.fr [this message] 2014-05-03 23:22 ` [Bug libfortran/61049] " jvdelisle at gcc dot gnu.org 2014-05-04 11:05 ` dominiq at lps dot ens.fr 2014-05-05 0:10 ` jvdelisle at gcc dot gnu.org 2014-05-05 0:11 ` jvdelisle at gcc dot gnu.org 2014-05-05 9:13 ` rguenth at gcc dot gnu.org 2014-05-05 9:16 ` dominiq at lps dot ens.fr 2014-05-07 1:32 ` jvdelisle at gcc dot gnu.org 2014-05-07 1:46 ` jvdelisle at gcc dot gnu.org 2014-05-11 3:48 ` jvdelisle at gcc dot gnu.org 2014-05-11 3:53 ` jvdelisle at gcc dot gnu.org 2014-05-11 4:33 ` 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-61049-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).