public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/25305] [4.0 regression]: libfortran failed fma3d in SPEC CPU 2K Date: Tue, 20 Dec 2005 05:06:00 -0000 [thread overview] Message-ID: <20051220050610.31202.qmail@sourceware.org> (raw) In-Reply-To: <bug-25305-682@http.gcc.gnu.org/bugzilla/> ------- Comment #15 from jvdelisle at gcc dot gnu dot org 2005-12-20 05:06 ------- Evidently I do not have authorization to commit to the 4.0 branch. (I tried twice) Here is a completed and ready testcase. I strongly suggest people move on to 4.1 if at all possible. If someone else wants to commit this, please do. ! { dg-do run } ! PR25305 Check for no end-of-record error on write after read. ! Derived from example given in PR by Grigory Zagorodnev. CHARACTER RD*8 CHARACTER WR*8 CHARACTER(1) C1 RD='N 1' READ (RD(1:2),*) C1 IF (C1.NE.'N') CALL ABORT WRITE (WR,*) 'passed' IF (WR.NE.' passed') CALL ABORT() END -- jvdelisle at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jvdelisle at gcc dot gnu dot|unassigned at gcc dot gnu |org |dot org Status|ASSIGNED |NEW http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25305
next prev parent reply other threads:[~2005-12-20 5:06 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-12-08 1:45 [Bug target/25305] New: [4.0]: -O2 miscompiled " hjl at lucon dot org 2005-12-08 1:56 ` [Bug target/25305] [4.0 regression]: " hjl at lucon dot org 2005-12-08 2:04 ` hjl at lucon dot org 2005-12-08 2:11 ` hjl at lucon dot org 2005-12-08 3:16 ` hjl at lucon dot org 2005-12-08 3:28 ` hjl at lucon dot org 2005-12-08 3:30 ` hjl at lucon dot org 2005-12-08 6:55 ` [Bug libfortran/25305] [4.0 regression]: libfortran failed " hjl at lucon dot org 2005-12-08 9:01 ` Jerry DeLisle 2005-12-08 7:32 ` hjl at lucon dot org 2005-12-08 9:01 ` jvdelisle at verizon dot net 2005-12-12 15:04 ` hjl at lucon dot org 2005-12-19 7:25 ` jvdelisle at gcc dot gnu dot org 2005-12-19 14:40 ` hjl at lucon dot org 2005-12-19 14:41 ` grigory_zagorodnev at linux dot intel dot com 2005-12-20 0:50 ` jvdelisle at gcc dot gnu dot org 2005-12-20 5:06 ` jvdelisle at gcc dot gnu dot org [this message] 2005-12-20 6:06 ` jvdelisle at gcc dot gnu dot org 2005-12-20 6:12 ` jvdelisle at gcc dot gnu dot org 2005-12-20 6:19 ` jvdelisle at gcc dot gnu dot org 2005-12-20 6:22 ` hjl at lucon dot org 2005-12-20 6:48 ` steven at gcc dot gnu dot org 2005-12-20 14:44 ` hjl at lucon dot org 2005-12-20 17:01 ` kargl at gcc dot gnu dot org 2006-01-01 5:28 ` pinskia 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=20051220050610.31202.qmail@sourceware.org \ --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).