public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl dot tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/39632] New: Revision 145497 caused extra failures on Linux/ia64 Date: Fri, 03 Apr 2009 22:46:00 -0000 [thread overview] Message-ID: <bug-39632-682@http.gcc.gnu.org/bugzilla/> (raw) Revision 145497: http://gcc.gnu.org/ml/gcc-cvs/2009-04/msg00118.html removed xfail on some testcases. But they still fail on Linux/ia64: FAIL: gcc.dg/vect/no-vfa-vect-43.c scan-tree-dump-times vect "Alignment of access forced using versioning" 1 FAIL: gcc.dg/vect/no-vfa-vect-57.c scan-tree-dump-times vect "vectorized 1 loops" 1 FAIL: gcc.dg/vect/no-vfa-vect-61.c scan-tree-dump-times vect "vectorized 1 loops" 1 -- Summary: Revision 145497 caused extra failures on Linux/ia64 Product: gcc Version: 4.5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: testsuite AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: hjl dot tools at gmail dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39632
next reply other threads:[~2009-04-03 22:46 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-04-03 22:46 hjl dot tools at gmail dot com [this message] 2009-04-21 16:58 ` [Bug testsuite/39632] " sje at cup dot hp dot com 2009-04-23 15:39 ` sje at cup dot hp 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=bug-39632-682@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: linkBe 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).