public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/50328] reduction with constant or invariant not vectorized Date: Fri, 09 Sep 2011 09:07:00 -0000 [thread overview] Message-ID: <bug-50328-4-8H3BELHF8m@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50328-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50328 --- Comment #6 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-09-09 09:05:39 UTC --- Ah, we fail outer loop vectorization because of a bug (versioning for alias required) and then drop into vectorizable_reduction with a statement with a operand def that is a PHI with vect_unused_in_scope which of course does not have its vector type set. It's also not marked live for some reason. Doh, seems to be a genuine swap_tree_operands bug.
next prev parent reply other threads:[~2011-09-09 9:06 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-09-08 13:30 [Bug tree-optimization/50328] New: loop interchange confuses vectorizer rguenth at gcc dot gnu.org 2011-09-08 13:37 ` [Bug tree-optimization/50328] " rguenth at gcc dot gnu.org 2011-09-08 13:42 ` rguenth at gcc dot gnu.org 2011-09-08 13:55 ` rguenth at gcc dot gnu.org 2011-09-08 14:09 ` [Bug tree-optimization/50328] reduction with constant or invariant not vectorized rguenth at gcc dot gnu.org 2011-09-08 14:22 ` rguenth at gcc dot gnu.org 2011-09-09 9:07 ` rguenth at gcc dot gnu.org [this message] 2011-09-09 12:37 ` rguenth at gcc dot gnu.org 2011-09-09 12:57 ` 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=bug-50328-4-8H3BELHF8m@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).