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/38199] [4.7/4.8/4.9 Regression] missed optimization: I/O performance Date: Mon, 10 Mar 2014 20:27:00 -0000 [thread overview] Message-ID: <bug-38199-4-Rt67KzjZmL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-38199-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38199 --- Comment #36 from Dominique d'Humieres <dominiq at lps dot ens.fr> --- When running the NIST tests from a script, I see the following failure with the patch: FM908 fails to run At line 727 of file /Users/dominiq/Documents/Fortran/NISTtest/NIST/FM908.f Fortran runtime error: Bad value on logical read However the test succeeds when run manually.
next prev parent reply other threads:[~2014-03-10 20:27 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-38199-4@http.gcc.gnu.org/bugzilla/> 2010-10-23 10:03 ` [Bug fortran/38199] " tkoenig at gcc dot gnu.org 2010-10-23 13:03 ` jvdelisle at gcc dot gnu.org 2011-05-10 9:55 ` jb at gcc dot gnu.org 2012-03-11 22:42 ` steven at gcc dot gnu.org 2012-03-15 15:19 ` [Bug libfortran/38199] " jb at gcc dot gnu.org 2012-03-19 9:45 ` manfred99 at gmx dot ch 2012-04-15 11:54 ` tkoenig at gcc dot gnu.org 2012-04-15 11:57 ` tkoenig at gcc dot gnu.org 2012-04-15 14:18 ` jvdelisle at gcc dot gnu.org 2012-04-17 19:38 ` burnus at gcc dot gnu.org 2012-04-18 9:03 ` manfred99 at gmx dot ch 2013-02-15 10:21 ` manfred99 at gmx dot ch 2013-02-15 11:28 ` [Bug libfortran/38199] [4.7/4.8 Regression] " burnus at gcc dot gnu.org 2013-02-17 11:25 ` tkoenig at gcc dot gnu.org 2013-04-11 7:58 ` [Bug libfortran/38199] [4.7/4.8/4.9 " rguenth at gcc dot gnu.org 2013-11-10 2:54 ` jvdelisle at gcc dot gnu.org 2013-11-10 22:08 ` jvdelisle at gcc dot gnu.org 2014-03-08 6:56 ` jvdelisle at gcc dot gnu.org 2014-03-08 23:59 ` manfred99 at gmx dot ch 2014-03-09 3:09 ` jvdelisle at gcc dot gnu.org 2014-03-09 3:18 ` jvdelisle at gcc dot gnu.org 2014-03-09 5:25 ` jvdelisle at gcc dot gnu.org 2014-03-09 5:35 ` jvdelisle at gcc dot gnu.org 2014-03-10 1:14 ` jvdelisle at gcc dot gnu.org 2014-03-10 20:06 ` dominiq at lps dot ens.fr 2014-03-10 20:27 ` dominiq at lps dot ens.fr [this message] 2014-03-11 3:38 ` dominiq at lps dot ens.fr 2014-03-11 4:52 ` jvdelisle at gcc dot gnu.org 2014-03-12 2:50 ` jvdelisle at gcc dot gnu.org 2014-03-12 15:16 ` dominiq at lps dot ens.fr 2014-03-13 5:07 ` jvdelisle at gcc dot gnu.org 2014-03-15 20:32 ` jvdelisle at gcc dot gnu.org 2014-03-15 23:07 ` jvdelisle at gcc dot gnu.org 2014-03-15 23:09 ` 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-38199-4-Rt67KzjZmL@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).