public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "irar at il dot ibm.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/50789] Gather vectorization
Date: Wed, 19 Oct 2011 08:49:00 -0000	[thread overview]
Message-ID: <bug-50789-4-EHx1dbSha6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50789-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50789

--- Comment #2 from Ira Rosen <irar at il dot ibm.com> 2011-10-19 08:47:03 UTC ---
(In reply to comment #0)

> To vectorize the above I'm afraid we'd need to modify tree-data-ref.c as well
> as tree-vect-data-ref.c, because the memory accesses aren't affine and already
> dr_analyze_innermost gives up on those, doesn't fill in any of the DR_* stuff.
> Perhaps with some flag and when the base resp. offset has vdef in the same loop
> we could mark it somehow and at least fill in the other fields.  It would
> probably make alias decisions (in tree-vect-data-ref.c?) harder.  Any ideas?

We have something similar for SLP: if an access is not affine we just fill in
what we can. But I don't really understand what can be filled in for f3/f4.

I don't think any data dependence decision is possible for f3 and f4, since we
can't prove anything. But in all the examples there are no stores, and we don't
care about read-read.

In f1 and f2 we know the base so, assuming no overflow, we can handle stores to
a different array.

> 
> What is additionally possible is to conditionalize loads, either affine or not.

Can't we treat it as an unconditional load for the dr analysis purposes?


  parent reply	other threads:[~2011-10-19  8:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-19  7:51 [Bug tree-optimization/50789] New: " jakub at gcc dot gnu.org
2011-10-19  8:10 ` [Bug tree-optimization/50789] " rguenth at gcc dot gnu.org
2011-10-19  8:49 ` irar at il dot ibm.com [this message]
2011-10-19  9:03 ` jakub at gcc dot gnu.org
2011-10-19  9:40 ` irar at il dot ibm.com
2011-10-24  8:40 ` jakub at gcc dot gnu.org
2011-10-25 21:17 ` jakub at gcc dot gnu.org
2011-10-26 16:57 ` jakub at gcc dot gnu.org
2011-11-07 16:02 ` jakub at gcc dot gnu.org
2011-11-08 13:26 ` jakub at gcc dot gnu.org
2013-04-02 16:50 ` vincenzo.innocente at cern dot ch
2013-04-17  8:31 ` andrey.turetskiy at gmail dot com
2013-04-17  8:53 ` rguenther at suse dot de
2013-07-03  9:22 ` vincenzo.innocente at cern dot ch

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-50789-4-EHx1dbSha6@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).