public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "victork at il dot ibm dot com" <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: Tue, 14 Feb 2006 12:20:00 -0000 [thread overview] Message-ID: <20060214122008.15183.qmail@sourceware.org> (raw) In-Reply-To: <bug-25918-230@http.gcc.gnu.org/bugzilla/> ------- Comment #9 from victork at il dot ibm dot com 2006-02-14 12:20 ------- Hello, I've prepared a patch to the testsuite to make dg-final checks more precise. The patch was tested on ppc64-yellowdog-linux. I have no access to IA64 box. Could someone check this patch on ia64? The patch can be found in "mainline.PR25918-2.patch.txt" attachment. Thanks, -- victor 2006-02-12 Victor Kaplansky <victork@il.ibm.com> PR tree-opt/25918 * lib/target-supports.exp (check_effective_target_vect_char_mult): New. (check_effective_target_vect_short_mult): New. (check_effective_target_vect_widen_sum_qi_to_si): New. (check_effective_target_vect_widen_sum_qi_to_hi): New. (check_effective_target_vect_widen_sum_hi_to_si): New. * gcc.dg/vect/vect-reduc-dot-s16.c: Remove, split into vect-reduc-dot-s16a.c and vect-reduc-dot-s16b.c * vect-reduc-dot-s16a.c: New, split from vect-reduc-dot-s16.c. * vect-reduc-dot-s16b.c: New, split from vect-reduc-dot-s16.c. * gcc.dg/vect/vect-reduc-pattern-2.c: Remove, split into vect-reduc-pattern-2a.c, vect-reduc-pattern-2b.c and vect-reduc-pattern-2c.c * gcc.dg/vect/vect-reduc-pattern-1.c: Remove, split into vect-reduc-pattern-1a.c, vect-reduc-pattern-1b.c and vect-reduc-pattern-1c.c -- victork at il dot ibm dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |victork at il dot ibm dot | |com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25918
next prev parent reply other threads:[~2006-02-14 12:20 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 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 [this message] 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=20060214122008.15183.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).