public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "wilson at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/25918] gcc.dg/vect/vect-reduc-dot-s16.c scan-tree-dump-times vectorized 1 loops 1 and gcc.dg/vect/vect-reduc-pattern-2.c scan-tree-dump-times vectorized 2 loops 1 fail Date: Wed, 08 Feb 2006 02:07:00 -0000 [thread overview] Message-ID: <20060208020748.19060.qmail@sourceware.org> (raw) In-Reply-To: <bug-25918-230@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from wilson at gcc dot gnu dot org 2006-02-08 02:07 ------- The vect-reduc-dot-s16.c testcase fails because two loops were vectorized, and we only expected one to be vectorized. The problem here is that the loop in foo1 is not supposed to be recognized and vectorized as a dot-product loop. And it isn't, as expected. However, on IA-64, it is recognized and vectorized as a widen-sum loop. This happens because the IA-64 port defines the widen_ssumv4hi3 pattern. The IA-64 port is the only one that defines this pattern, and hence is probably the only port "broken" here. All others will presumably fail to vectorize this loop. So the IA-64 port emits to the -fdump-tree-vect-details file tmp.c:23: note: pattern recognized: prod_14 w+ result_3 tmp.c:23: note: vectorized 1 loops in function. tmp.c:38: note: pattern recognized: DOT_PROD_EXPR < D.2127_14 , D.2125_10 ... tmp.c:38: note: vectorized 1 loops in function. and the testcase fails because we only expected 1 loop to be vectorized. I think the only thing wrong here is that the dg-final tests in the testcase are not precise enough to handle this case. -- wilson at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfirmed|0000-00-00 00:00:00 |2006-02-08 02:07:47 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25918
next prev parent reply other threads:[~2006-02-08 2:07 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-01-23 0:53 [Bug tree-optimization/25918] New: " jsm28 at gcc dot gnu dot org 2006-01-26 9:07 ` [Bug tree-optimization/25918] " dorit at il dot ibm dot com 2006-01-28 17:04 ` jsm28 at gcc dot gnu dot org 2006-01-28 17:05 ` jsm28 at gcc dot gnu dot org 2006-02-08 2:07 ` wilson at gcc dot gnu dot org [this message] 2006-02-08 2:19 ` wilson at gcc dot gnu dot org 2006-02-08 14:18 ` dorit at il dot ibm dot com 2006-02-08 14:19 ` dorit at il dot ibm dot com 2006-02-14 12:16 ` victork at il dot ibm dot com 2006-02-14 12:20 ` victork at il dot ibm dot com 2006-02-14 23:41 ` wilson at tuliptree dot org 2006-02-16 9:59 ` victork at gcc dot gnu dot org 2006-02-16 17:43 ` [Bug testsuite/25918] " pinskia at gcc dot gnu dot 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=20060208020748.19060.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).