public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/45151] [4.6 regression] New Fortran failuires
Date: Tue, 03 Aug 2010 09:44:00 -0000 [thread overview]
Message-ID: <20100803094439.22970.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45151-682@http.gcc.gnu.org/bugzilla/>
------- Comment #12 from burnus at gcc dot gnu dot org 2010-08-03 09:44 -------
This PR seems to be mostly fixed:
- x86_64-unknown-linux-gnu shows _no_ failures (-m32/-m64)
http://gcc.gnu.org/ml/gcc-testresults/2010-08/msg00217.html
- ia64-unknown-linux-gnu shows _two_ failures:
http://gcc.gnu.org/ml/gcc-testresults/2010-08/msg00213.html
FAIL: gfortran.dg/maxlocval_3.f90 -O3 -fomit-frame-pointer -funroll-loops
(test for excess errors)
FAIL: gfortran.dg/maxlocval_3.f90 -O3 -fomit-frame-pointer -funroll-all-loops
-finline-functions (test for excess errors)
FAIL: gfortran.dg/typebound_proc_15.f03 -O (internal compiler error)
FAIL: gfortran.dg/typebound_proc_15.f03 -O (test for excess errors)
The latter is PR 44584 for which a patch has just been posted.
HJ: Can you confirm that all failures are now gone (pending the PR 44584
committal), except for maxlocval_3.f90?
Can you post the excess error which is shown for maxlocval_3.f90?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45151
next prev parent reply other threads:[~2010-08-03 9:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-31 15:30 [Bug fortran/45151] New: " hjl dot tools at gmail dot com
2010-07-31 15:37 ` [Bug fortran/45151] " dominiq at lps dot ens dot fr
2010-08-01 12:23 ` mikael at gcc dot gnu dot org
2010-08-01 12:30 ` rguenth at gcc dot gnu dot org
2010-08-01 12:39 ` janus at gcc dot gnu dot org
2010-08-01 12:50 ` janus at gcc dot gnu dot org
2010-08-01 12:52 ` mikael at gcc dot gnu dot org
2010-08-01 12:54 ` mikael at gcc dot gnu dot org
2010-08-01 13:12 ` mikael at gcc dot gnu dot org
2010-08-01 21:30 ` janus at gcc dot gnu dot org
2010-08-01 22:29 ` mikael at gcc dot gnu dot org
2010-08-02 5:24 ` dominiq at lps dot ens dot fr
2010-08-02 15:31 ` mikael at gcc dot gnu dot org
2010-08-03 9:44 ` burnus at gcc dot gnu dot org [this message]
2010-08-03 14:24 ` hjl dot tools at gmail dot com
2010-08-03 15:42 ` sje at cup dot hp dot com
2010-08-03 16:13 ` burnus at gcc dot gnu dot org
2010-08-05 21:09 ` mikael 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=20100803094439.22970.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: link
Be 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).