public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/37021] Fortran Complex reduction / multiplication not vectorized Date: Fri, 23 Jan 2009 15:36:00 -0000 [thread overview] Message-ID: <20090123153608.25150.qmail@sourceware.org> (raw) In-Reply-To: <bug-37021-10053@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from rguenth at gcc dot gnu dot org 2009-01-23 15:36 ------- So, 4) The vectorized version sucks because we have to use peeling for niters because we need to unroll the loop once and cannot apply SLP here. Q1: does SLP work with reductions at all? Q2: does SLP do pattern recognition? First of all we would need to recognize a complex reduction as a single vectorized reduction. Second we need to vectorize the complex multiplication with SLP, feeding the reduction with one resulting complex vector. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37021
next prev parent reply other threads:[~2009-01-23 15:36 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-08-04 17:57 [Bug tree-optimization/37021] New: " rguenth at gcc dot gnu dot org 2008-08-04 17:59 ` [Bug tree-optimization/37021] " rguenth at gcc dot gnu dot org 2008-08-19 15:31 ` rguenth at gcc dot gnu dot org 2009-01-21 15:43 ` rguenth at gcc dot gnu dot org 2009-01-23 15:33 ` rguenth at gcc dot gnu dot org 2009-01-23 15:36 ` rguenth at gcc dot gnu dot org [this message] 2009-01-25 9:13 ` irar at il dot ibm dot com 2009-01-25 11:04 ` rguenther at suse dot de 2009-01-25 12:17 ` irar at il dot ibm dot com 2009-01-27 12:40 ` dorit at gcc dot gnu dot org [not found] <bug-37021-4@http.gcc.gnu.org/bugzilla/> 2011-03-25 11:49 ` sebastian.hegler@tu-dresden.de 2011-03-25 12:27 ` sebastian.hegler@tu-dresden.de 2011-03-25 13:13 ` rguenther at suse dot de 2012-07-13 8:46 ` rguenth at gcc dot gnu.org 2013-02-13 15:58 ` rguenth at gcc dot gnu.org 2013-03-27 10:39 ` rguenth at gcc dot gnu.org 2013-03-27 10:40 ` rguenth at gcc dot gnu.org 2013-04-07 13:18 ` dominiq at lps dot ens.fr 2015-05-12 11:56 ` rguenth at gcc dot gnu.org 2015-06-10 10:45 ` rguenth at gcc dot gnu.org 2015-08-25 8:11 ` rguenth at gcc dot gnu.org 2015-08-27 22:09 ` wschmidt at gcc dot gnu.org 2015-08-28 7:46 ` rguenther at suse dot de 2015-08-28 13:20 ` wschmidt at gcc dot gnu.org 2015-08-28 13:31 ` wschmidt at gcc dot gnu.org 2015-10-22 10:03 ` rguenth at gcc dot gnu.org 2023-07-21 12:28 ` rguenth 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=20090123153608.25150.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).