public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/50632] New: [4.7 Regression] New test failures
Date: Thu, 06 Oct 2011 15:59:00 -0000 [thread overview]
Message-ID: <bug-50632-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50632
Bug #: 50632
Summary: [4.7 Regression] New test failures
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: hjl.tools@gmail.com
On Linux/x86-64, revision 179566 gave
FAIL: gcc.dg/pr50132.c (internal compiler error)
FAIL: gcc.dg/pr50132.c (test for excess errors)
FAIL: gfortran.fortran-torture/execute/entry_4.f90 execution, -O2
FAIL: gfortran.fortran-torture/execute/entry_4.f90 execution, -O2
-fbounds-check
FAIL: gfortran.fortran-torture/execute/entry_4.f90 execution, -O2
-fomit-frame-pointer -finline-functions
FAIL: gfortran.fortran-torture/execute/entry_4.f90 execution, -O2
-fomit-frame-pointer -finline-functions -funroll-loops
FAIL: gfortran.fortran-torture/execute/entry_4.f90 execution, -O3 -g
FAIL: gfortran.fortran-torture/execute/entry_4.f90 execution, -O2
-ftree-vectorize -msse2
Revision 179528 is OK.
next reply other threads:[~2011-10-06 15:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-06 15:59 hjl.tools at gmail dot com [this message]
2011-10-06 17:12 ` [Bug middle-end/50632] " hjl.tools at gmail dot com
2011-10-06 19:05 ` [Bug middle-end/50632] [4.7 Regression] FAIL: gcc.dg/pr50132.c rth at gcc dot gnu.org
2011-10-06 19:16 ` rth at gcc dot gnu.org
2011-10-06 22:23 ` rth at gcc dot gnu.org
2011-10-06 22:34 ` rth 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-50632-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: 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).