public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howarth at nitro dot med.uc.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/46892] New: gcc.dg/vect/vect-25.c failures with -fgraphite-identity
Date: Sat, 11 Dec 2010 04:34:00 -0000 [thread overview]
Message-ID: <bug-46892-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46892
Summary: gcc.dg/vect/vect-25.c failures with
-fgraphite-identity
Product: gcc
Version: 4.6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: howarth@nitro.med.uc.edu
The gcc.dg/vect/vect-25.c testcase fails at -m32 and -m64 on
x86_64-apple-darwin10 when -fgraphite-identity is used.
Executing on host: /sw/src/fink.build/gcc46-4.6.0-1000/darwin_objdir/gcc/xgcc
-B/sw/src/fink.build/gcc46-4.6.0-1000/darwin_objdir/gcc/
/sw/src/fink.build/gcc46-4.6.0-1000/gcc-4.6-20101210/gcc/testsuite/gcc.dg/vect/vect-25.c
-msse2 -ftree-vectorize -fno-vect-cost-model -O2 -fdump-tree-vect-details
-lm -m32 -o ./vect-25.exe (timeout = 300)
PASS: gcc.dg/vect/vect-25.c (test for excess errors)
Setting LD_LIBRARY_PATH to
:/sw/src/fink.build/gcc46-4.6.0-1000/darwin_objdir/gcc::/sw/src/fink.build/gcc46-4.6.0-1000/darwin_objdir/gcc
FAIL: gcc.dg/vect/vect-25.c execution test
FAIL: gcc.dg/vect/vect-25.c scan-tree-dump-times vect "vectorized 2 loops" 1
PASS: gcc.dg/vect/vect-25.c scan-tree-dump-times vect "Vectorizing an unaligned
access" 0
next reply other threads:[~2010-12-11 4:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-11 4:34 howarth at nitro dot med.uc.edu [this message]
2010-12-11 4:35 ` [Bug middle-end/46892] " howarth at nitro dot med.uc.edu
2010-12-11 4:40 ` howarth at nitro dot med.uc.edu
2010-12-11 4:40 ` howarth at nitro dot med.uc.edu
2010-12-11 4:52 ` howarth at nitro dot med.uc.edu
2010-12-11 4:56 ` howarth at nitro dot med.uc.edu
2010-12-11 4:56 ` howarth at nitro dot med.uc.edu
2010-12-23 3:43 ` howarth at nitro dot med.uc.edu
2011-01-09 16:07 ` howarth at nitro dot med.uc.edu
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-46892-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).