public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "davek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/46195] r165965 regresses i386 darwin
Date: Tue, 02 Nov 2010 05:30:00 -0000 [thread overview]
Message-ID: <20101102053000.aQIEpuUxlnBCPPliqKPw-c0xdmXH8sNcYUPzq2AQNz4@z> (raw)
In-Reply-To: <bug-46195-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46195
Dave Korn <davek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |davek at gcc dot gnu.org
--- Comment #25 from Dave Korn <davek at gcc dot gnu.org> 2010-11-02 05:30:01 UTC ---
Hi HJ, I'm getting a ton of failures caused by this same warning message at
r166110 on i686-pc-cygwin:
FAIL: gcc.dg/tree-ssa/forwprop-5.c (test for excess errors)
FAIL: gcc.dg/tree-ssa/fre-vce-1.c (test for excess errors)
FAIL: gcc.dg/tree-ssa/sra-4.c (test for excess errors)
FAIL: gcc.dg/tree-ssa/vector-1.c (test for excess errors)
FAIL: gcc.dg/tree-ssa/vector-2.c (test for excess errors)
FAIL: gcc.c-torture/execute/va-arg-25.c compilation, -O0
FAIL: gcc.c-torture/execute/va-arg-25.c compilation, -O1
FAIL: gcc.c-torture/execute/va-arg-25.c compilation, -O2
FAIL: gcc.c-torture/execute/va-arg-25.c compilation, -O3 -fomit-frame-pointer
FAIL: gcc.c-torture/execute/va-arg-25.c compilation, -O3 -g
FAIL: gcc.c-torture/execute/va-arg-25.c compilation, -Os
FAIL: gcc.c-torture/execute/va-arg-25.c compilation, -O2 -flto
FAIL: gcc.c-torture/execute/va-arg-25.c compilation, -O2 -fwhopr
FAIL: gcc.c-torture/execute/vector-1.c compilation, -O0
FAIL: gcc.c-torture/execute/vector-1.c compilation, -O1
FAIL: gcc.c-torture/execute/vector-1.c compilation, -O2
FAIL: gcc.c-torture/execute/vector-1.c compilation, -O3 -fomit-frame-pointer
FAIL: gcc.c-torture/execute/vector-1.c compilation, -O3 -g
FAIL: gcc.c-torture/execute/vector-1.c compilation, -Os
FAIL: gcc.c-torture/execute/vector-1.c compilation, -O2 -flto
FAIL: gcc.c-torture/execute/vector-1.c compilation, -O2 -fwhopr
FAIL: gcc.c-torture/execute/vector-2.c compilation, -O0
FAIL: gcc.c-torture/execute/vector-2.c compilation, -O1
FAIL: gcc.c-torture/execute/vector-2.c compilation, -O2
FAIL: gcc.c-torture/execute/vector-2.c compilation, -O3 -fomit-frame-pointer
FAIL: gcc.c-torture/execute/vector-2.c compilation, -O3 -g
FAIL: gcc.c-torture/execute/vector-2.c compilation, -Os
FAIL: gcc.c-torture/execute/vector-2.c compilation, -O2 -flto
FAIL: gcc.c-torture/execute/vector-2.c compilation, -O2 -fwhopr
FAIL: gcc.c-torture/compile/pr34856.c (test for excess errors)
FAIL: gcc.c-torture/compile/pr34856.c (test for excess errors)
FAIL: gcc.c-torture/compile/pr34856.c (test for excess errors)
FAIL: gcc.c-torture/compile/pr34856.c (test for excess errors)
FAIL: gcc.c-torture/compile/pr34856.c (test for excess errors)
FAIL: gcc.c-torture/compile/pr34856.c (test for excess errors)
FAIL: gcc.c-torture/compile/pr34856.c (test for excess errors)
FAIL: gcc.c-torture/compile/pr34856.c (test for excess errors)
FAIL: gcc.c-torture/compile/pr34856.c (test for excess errors)
FAIL: gcc.c-torture/compile/pr34856.c (test for excess errors)
FAIL: gcc.c-torture/compile/pr39928-1.c (test for excess errors)
FAIL: gcc.c-torture/compile/pr39928-1.c (test for excess errors)
FAIL: gcc.c-torture/compile/pr39928-1.c (test for excess errors)
FAIL: gcc.c-torture/compile/pr39928-1.c (test for excess errors)
FAIL: gcc.c-torture/compile/pr39928-1.c (test for excess errors)
FAIL: gcc.c-torture/compile/pr39928-1.c (test for excess errors)
FAIL: gcc.c-torture/compile/pr39928-1.c (test for excess errors)
FAIL: gcc.c-torture/compile/pr39928-1.c (test for excess errors)
FAIL: gcc.c-torture/compile/vector-1.c (test for excess errors)
FAIL: gcc.c-torture/compile/vector-1.c (test for excess errors)
FAIL: gcc.c-torture/compile/vector-1.c (test for excess errors)
FAIL: gcc.c-torture/compile/vector-1.c (test for excess errors)
FAIL: gcc.c-torture/compile/vector-1.c (test for excess errors)
FAIL: gcc.c-torture/compile/vector-1.c (test for excess errors)
FAIL: gcc.c-torture/compile/vector-1.c (test for excess errors)
FAIL: gcc.c-torture/compile/vector-1.c (test for excess errors)
FAIL: gcc.c-torture/compile/vector-2.c (test for excess errors)
FAIL: gcc.c-torture/compile/vector-2.c (test for excess errors)
FAIL: gcc.c-torture/compile/vector-2.c (test for excess errors)
FAIL: gcc.c-torture/compile/vector-2.c (test for excess errors)
FAIL: gcc.c-torture/compile/vector-2.c (test for excess errors)
FAIL: gcc.c-torture/compile/vector-2.c (test for excess errors)
FAIL: gcc.c-torture/compile/vector-2.c (test for excess errors)
FAIL: gcc.c-torture/compile/vector-2.c (test for excess errors)
FAIL: gcc.dg/pr32912-1.c (test for excess errors)
FAIL: gcc.target/i386/vect-args.c (test for excess errors)
FAIL: gcc.target/i386/vect-args.c (test for excess errors)
FAIL: gcc.target/i386/vect-args.c (test for excess errors)
FAIL: gcc.target/i386/vect-args.c (test for excess errors)
FAIL: gcc.target/i386/vect-args.c (test for excess errors)
FAIL: gcc.target/i386/vect-args.c (test for excess errors)
FAIL: gcc.target/i386/vect-args.c (test for excess errors)
FAIL: gcc.target/i386/vect-args.c (test for excess errors)
Should I reopen this bug or file a new one?
next prev parent reply other threads:[~2010-11-02 5:30 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 1:26 [Bug middle-end/46195] New: " howarth at nitro dot med.uc.edu
2010-10-27 1:46 ` [Bug middle-end/46195] " hjl.tools at gmail dot com
2010-10-27 1:46 ` hjl.tools at gmail dot com
2010-10-27 3:20 ` howarth at nitro dot med.uc.edu
2010-10-27 3:20 ` howarth at nitro dot med.uc.edu
2010-10-27 3:22 ` howarth at nitro dot med.uc.edu
2010-10-27 10:51 ` hjl.tools at gmail dot com
2010-10-27 10:51 ` [Bug target/46195] " hjl.tools at gmail dot com
2010-10-27 11:27 ` hjl.tools at gmail dot com
2010-10-27 12:14 ` hjl.tools at gmail dot com
2010-10-27 13:22 ` howarth at nitro dot med.uc.edu
2010-10-27 13:31 ` howarth at nitro dot med.uc.edu
2010-10-27 13:33 ` howarth at nitro dot med.uc.edu
2010-10-27 13:35 ` howarth at nitro dot med.uc.edu
2010-10-27 15:23 ` hjl.tools at gmail dot com
2010-10-27 16:18 ` howarth at nitro dot med.uc.edu
2010-10-27 19:04 ` howarth at nitro dot med.uc.edu
2010-10-27 22:35 ` howarth at nitro dot med.uc.edu
2010-10-27 22:36 ` howarth at nitro dot med.uc.edu
2010-10-27 22:37 ` howarth at nitro dot med.uc.edu
2010-10-28 0:43 ` howarth at nitro dot med.uc.edu
2010-10-28 5:46 ` hjl.tools at gmail dot com
2010-10-28 13:10 ` howarth at nitro dot med.uc.edu
2010-10-28 17:34 ` hjl.tools at gmail dot com
2010-10-28 18:12 ` howarth at nitro dot med.uc.edu
2010-10-30 13:17 ` hjl at gcc dot gnu.org
2010-10-30 13:26 ` hjl.tools at gmail dot com
2010-11-02 5:30 ` davek at gcc dot gnu.org [this message]
2010-11-02 12:04 ` hjl.tools at gmail dot com
2010-11-03 10:47 ` ebotcazou at gcc dot gnu.org
2010-11-03 12:10 ` hjl.tools at gmail dot com
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=20101102053000.aQIEpuUxlnBCPPliqKPw-c0xdmXH8sNcYUPzq2AQNz4@z \
--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).