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/65206] Vectorized version of loop is removed.
Date: Thu, 26 Feb 2015 12:15:00 -0000	[thread overview]
Message-ID: <bug-65206-4-PfLjQyEX5E@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65206-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65206

--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
Created attachment 34882
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34882&action=edit
hack just for the masked load/store case

Incomplete special-casing for the masked load/store case.  We need to mark
the masked load/store IFN calls somehow to mark the forwarding as valid.

A "real" fix would "duplicate" dr->indices to always have an alternate
analysis for *&dr->ref in case dr->ref is not a pointer evolution.  We
could then pick the one with compatible dr->indices.base_object.  Of course
that may still not handle all cases, if the ptr evolution is not enough
(like for having a[2][j] vs. *(&a[3][j])).  But at least it could help in
some general cases.


  parent reply	other threads:[~2015-02-26 11:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-25 14:50 [Bug tree-optimization/65206] New: " ysrumyan at gmail dot com
2015-02-25 14:55 ` [Bug tree-optimization/65206] " ysrumyan at gmail dot com
2015-02-25 15:08 ` rguenth at gcc dot gnu.org
2015-02-25 15:11 ` rguenth at gcc dot gnu.org
2015-02-25 15:30 ` rguenth at gcc dot gnu.org
2015-02-25 15:33 ` rguenth at gcc dot gnu.org
2015-02-26 12:15 ` rguenth at gcc dot gnu.org [this message]
2015-02-26 12:38 ` rguenth at gcc dot gnu.org
2021-09-08 11:08 ` rguenth at gcc dot gnu.org
2021-09-20  6:51 ` [Bug tree-optimization/65206] vectorized version of loop is removed, dependence analysis fails for *&a[i] vs a[j] cvs-commit at gcc dot gnu.org
2021-09-20  6:51 ` rguenth at gcc dot gnu.org
2022-03-29 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-65206-4-PfLjQyEX5E@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: link
Be 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).