public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "irar at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/41881] [4.5/4.6/4.7 regression] Complete unrolling (inner) versus vectorization of reduction Date: Wed, 18 May 2011 12:07:00 -0000 [thread overview] Message-ID: <bug-41881-4-HOY6EanomH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-41881-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41881 --- Comment #10 from irar at gcc dot gnu.org 2011-05-18 11:27:56 UTC --- Author: irar Date: Wed May 18 11:27:51 2011 New Revision: 173856 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=173856 Log: PR tree-optimization/41881 * tree-vectorizer.h (struct _loop_vec_info): Add new field reduction_chains along with a macro for its access. * tree-vect-loop.c (new_loop_vec_info): Initialize reduction chains. (destroy_loop_vec_info): Free reduction chains. (vect_analyze_loop_2): Return false if vect_analyze_slp() returns false. (vect_is_slp_reduction): New function. (vect_is_simple_reduction_1): Call vect_is_slp_reduction. (vect_create_epilog_for_reduction): Support SLP reduction chains. * tree-vect-slp.c (vect_get_and_check_slp_defs): Allow different definition types for reduction chains. (vect_supported_load_permutation_p): Don't allow permutations for reduction chains. (vect_analyze_slp_instance): Support reduction chains. (vect_analyze_slp): Try to build SLP instance from reduction chains. (vect_get_constant_vectors): Handle reduction chains. (vect_schedule_slp_instance): Mark the first statement of the reduction chain as reduction. Added: trunk/gcc/testsuite/gcc.dg/vect/O3-pr41881.c trunk/gcc/testsuite/gcc.dg/vect/O3-slp-reduc-10.c Modified: trunk/gcc/ChangeLog trunk/gcc/testsuite/ChangeLog trunk/gcc/tree-vect-loop.c trunk/gcc/tree-vect-slp.c trunk/gcc/tree-vectorizer.h
next prev parent reply other threads:[~2011-05-18 11:48 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-41881-4@http.gcc.gnu.org/bugzilla/> 2010-12-16 13:12 ` [Bug tree-optimization/41881] [4.5/4.6 " rguenth at gcc dot gnu.org 2011-04-28 15:35 ` [Bug tree-optimization/41881] [4.5/4.6/4.7 " rguenth at gcc dot gnu.org 2011-05-18 12:07 ` irar at gcc dot gnu.org [this message] 2011-05-18 12:13 ` irar at il dot ibm.com 2012-01-05 17:15 ` [Bug tree-optimization/41881] [4.5/4.6 " jakub at gcc dot gnu.org 2012-07-02 11:38 ` rguenth at gcc dot gnu.org 2013-04-12 16:18 ` [Bug tree-optimization/41881] [4.6 " jakub at gcc dot gnu.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=bug-41881-4-HOY6EanomH@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).