public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "matz at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/39300] vectorizer confused by predictive commoning and PRE Date: Wed, 22 Jul 2009 15:40:00 -0000 [thread overview] Message-ID: <20090722154026.25423.qmail@sourceware.org> (raw) In-Reply-To: <bug-39300-12182@http.gcc.gnu.org/bugzilla/> ------- Comment #8 from matz at gcc dot gnu dot org 2009-07-22 15:40 ------- So, the immediate problem is now fixed, but I'd suggest leaving this enhancement request open, in case anybody wants to work on extending the vectorizer to deal with these loop-carried dependencies, because in that case we wouldn't need to dumb down PRE anymore, which would be even better. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39300
next prev parent reply other threads:[~2009-07-22 15:40 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-02-25 12:16 [Bug tree-optimization/39300] New: vectorizer confused by predictive commoning matz at gcc dot gnu dot org 2009-02-25 13:53 ` [Bug tree-optimization/39300] " matz at gcc dot gnu dot org 2009-02-25 13:56 ` rguenth at gcc dot gnu dot org 2009-02-25 14:07 ` [Bug tree-optimization/39300] vectorizer confused by predictive commoning and PRE rguenth at gcc dot gnu dot org 2009-02-25 14:08 ` irar at il dot ibm dot com 2009-03-08 14:26 ` dorit at gcc dot gnu dot org 2009-03-09 13:25 ` matz at gcc dot gnu dot org 2009-07-22 15:31 ` matz at gcc dot gnu dot org 2009-07-22 15:40 ` matz at gcc dot gnu dot org [this message] 2009-08-17 17:39 ` jessiecute13 at aol dot com [not found] <bug-39300-4@http.gcc.gnu.org/bugzilla/> 2012-07-13 8:51 ` rguenth at gcc dot gnu.org 2012-07-19 11:42 ` 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=20090722154026.25423.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).