public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "michael.hope at linaro dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/47976] [4.5 Regression] Recent gfortran.dg/actual_array_constructor_3.f90 regression on arm-linux-gnueabi
Date: Tue, 15 Mar 2011 02:19:00 -0000 [thread overview]
Message-ID: <bug-47976-4-I7RitBemat@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47976-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47976
Michael Hope <michael.hope at linaro dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |michael.hope at linaro dot
| |org
--- Comment #3 from Michael Hope <michael.hope at linaro dot org> 2011-03-15 02:07:16 UTC ---
The failure also exists in 4.6.0 20110308 [trunk revision 170780]. See:
https://lists.launchpad.net/linaro-toolchain-builds/msg00290.html
for test results. Sorry that these aren't posted to gcc-testresults@gcc yet
but I'm ironing out kinks.
Running target unix
FAIL: gfortran.dg/actual_array_constructor_3.f90 -O3 -fomit-frame-pointer
-funroll-loops execution test
FAIL: gfortran.dg/actual_array_constructor_3.f90 -O3 -fomit-frame-pointer
-funroll-all-loops -finline-functions execution test
FAIL: gfortran.dg/pr45636.f90 -O scan-tree-dump-times forwprop2 "memset" 0
WARNING: program timed out.
FAIL: gfortran.dg/vect/fast-math-pr38968.f90 execution test
FAIL: gfortran.dg/vect/fast-math-pr38968.f90 scan-tree-dump vect "vectorized 1
loops"
WARNING: program timed out.
FAIL: gfortran.fortran-torture/execute/entry_6.f90 compilation, -O2
next prev parent reply other threads:[~2011-03-15 2:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 15:38 [Bug target/47976] New: Recent fortran testsuite regressions ams at gcc dot gnu.org
2011-03-04 11:03 ` [Bug fortran/47976] " burnus at gcc dot gnu.org
2011-03-08 8:35 ` [Bug fortran/47976] [4.5 Regression] Recent gfortran.dg/actual_array_constructor_3.f90 regression on arm-linux-gnueabi burnus at gcc dot gnu.org
2011-03-15 2:19 ` michael.hope at linaro dot org [this message]
2011-03-16 21:27 ` michael.hope at linaro dot org
2011-03-20 22:00 ` michael.hope at linaro dot org
2011-04-04 20:42 ` ramana at gcc dot gnu.org
2011-04-04 21:32 ` ramana at gcc dot gnu.org
2011-04-10 10:36 ` [Bug middle-end/47976] [4.5/4.6/4.7 " rguenth at gcc dot gnu.org
2011-04-11 9:04 ` ramana at gcc dot gnu.org
2011-04-15 12:11 ` bernds at gcc dot gnu.org
2011-04-19 1:05 ` michael.hope at linaro dot org
2011-04-19 10:56 ` rguenth at gcc dot gnu.org
2011-04-19 11:05 ` [Bug middle-end/47976] [4.5/4.6 " rguenth at gcc dot gnu.org
2011-04-20 9:49 ` rguenth at gcc dot gnu.org
2011-04-20 11:07 ` rguenth at gcc dot gnu.org
2011-04-20 11:08 ` rguenth 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-47976-4-I7RitBemat@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: 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).