public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "irar at il dot ibm dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/40359] [4.5 Regression] Revision 148211 caused a lot of failures in the vect test suite. Date: Wed, 17 Jun 2009 11:06:00 -0000 [thread overview] Message-ID: <20090617110603.12458.qmail@sourceware.org> (raw) In-Reply-To: <bug-40359-12313@http.gcc.gnu.org/bugzilla/> ------- Comment #25 from irar at il dot ibm dot com 2009-06-17 11:06 ------- (In reply to comment #24) > If I add to vect-42.c (with my patch) the line > > /* { dg-final { scan-tree-dump-times "bla bla bla" 1 "vect" { target vector_alignment_reachable } } } */ ... > i.e., the test is done for -m32 (and fail) but not for -m64. So, vector_alignment_reachable is true for -m32 and false for -m64. ... > i.e., vect_hw_misalign is false for both -m32 and -m64. > So it looks that vect_hw_misalign has the opposite meaning of that assumed in > comment #16: > > hmmm... versioning should not be done for targets that support > > vect_hw_misalign... Why? vect_hw_misalign means that misaligned data acceses are supported by hardware, therefore, we don't need to do versioning. And we expect versioning here with -m64 since both vect_hw_misalign and vector_alignment_reachable are false. > Final note, the change in comment #17 does not help. Thanks for checking. I still don't understand why this test works on -m64 /* { dg-final { scan-tree-dump-times "Alignment of access forced using peeling" 1 "vect" { xfail { { vect_no_align || vect_hw_misalign } || { ! vector_alignment_reachable } } } } } */ vector_alignment_reachable is false, so there should be no peeling according to the test. But it is there, and the test doesn't XPASS... And, of course, I don't understand why we do peeling, i.e., builtin vector_alignment_reachable returns true. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40359
next prev parent reply other threads:[~2009-06-17 11:06 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-06-06 9:15 [Bug testsuite/40359] New: " dominiq at lps dot ens dot fr 2009-06-06 11:00 ` [Bug testsuite/40359] " eres at il dot ibm dot com 2009-06-06 15:49 ` dominiq at lps dot ens dot fr 2009-06-06 16:44 ` eres at il dot ibm dot com 2009-06-06 16:46 ` eres at il dot ibm dot com 2009-06-06 17:24 ` dominiq at lps dot ens dot fr 2009-06-06 17:32 ` eres at il dot ibm dot com 2009-06-07 6:38 ` dominiq at lps dot ens dot fr 2009-06-07 7:12 ` eres at il dot ibm dot com 2009-06-07 7:48 ` dominiq at lps dot ens dot fr 2009-06-07 10:51 ` eres at il dot ibm dot com 2009-06-12 12:00 ` dominiq at lps dot ens dot fr 2009-06-13 19:13 ` pinskia at gcc dot gnu dot org 2009-06-15 9:58 ` irar at il dot ibm dot com 2009-06-15 10:41 ` eres at il dot ibm dot com 2009-06-15 12:37 ` dominiq at lps dot ens dot fr 2009-06-15 12:46 ` dominiq at lps dot ens dot fr 2009-06-15 13:33 ` eres at il dot ibm dot com 2009-06-16 7:36 ` irar at il dot ibm dot com 2009-06-16 10:10 ` dominiq at lps dot ens dot fr 2009-06-16 10:18 ` irar at il dot ibm dot com 2009-06-16 10:26 ` dominiq at lps dot ens dot fr 2009-06-16 11:08 ` irar at il dot ibm dot com 2009-06-16 13:14 ` dominiq at lps dot ens dot fr 2009-06-17 8:23 ` irar at il dot ibm dot com 2009-06-17 10:17 ` dominiq at lps dot ens dot fr 2009-06-17 11:06 ` irar at il dot ibm dot com [this message] 2009-06-17 11:59 ` dominiq at lps dot ens dot fr 2009-06-17 12:04 ` dominiq at lps dot ens dot fr 2009-06-17 12:12 ` dominiq at lps dot ens dot fr 2009-06-17 12:40 ` irar at il dot ibm dot com 2009-06-17 12:48 ` dominiq at lps dot ens dot fr 2009-06-18 8:03 ` irar at il dot ibm dot com 2009-06-18 8:46 ` dominiq at lps dot ens dot fr 2009-06-18 9:14 ` irar at il dot ibm dot com 2009-06-18 12:59 ` dominiq at lps dot ens dot fr 2009-06-18 14:07 ` eres at il dot ibm dot com 2009-07-06 9:03 ` dominiq at lps dot ens dot fr
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=20090617110603.12458.qmail@sourceware.org \ --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).