public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ira Rosen <IRAR@il.ibm.com>
To: Abhishek Shrivastav <abhishek.shrivastav24@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Inner loop unable to compute sufficient information during   	vectorization
Date: Tue, 26 May 2009 13:54:00 -0000	[thread overview]
Message-ID: <OF22C16181.5F6FF996-ONC22575C2.0043892B-C22575C2.0044711F@il.ibm.com> (raw)
In-Reply-To: <4f5553710905251153q2eda011bqe288f37b3fb0fea@mail.gmail.com>



gcc-owner@gcc.gnu.org wrote on 25/05/2009 21:53:41:

> for a loop like
>
> 1         for(i=0;i<N;i++)
> 2           for(j=0;j<N;j++)
> 3               a[i][j] = a[i][j]+b[i][j];
>
> GCC 4.3.* is unable to get the information for the inner loop that
> array reference 'a'  is alias of each other and generates code for
> runtime aliasing check during vectorization.

Both current trunk and GCC4.4 vectorize the inner loop without any runtime
alias checks.

> Is it necessary to
> recompute all information in loop_vec_info in function
> vect_analyze_ref for analysis of inner loop also, as most of the
> information is similar for the outer loop for the program.

Maybe you are right, and it is possible to extract at least part of the
information for the inner loop from the outer loop information.

>
> Similarly, outer loop is able to compute correct chrec i.e. NULL , for
> array 'a' reference, while innerloop has chrec as chrec_dont_know, and
> therfore complaint about runtime alias check.

The chrecs are not the same for inner and outer loops, so it is reasonable
that the results of the data dependence tests will be different.
In this case, however, it seems to be a bug.

Ira



  reply	other threads:[~2009-05-26 12:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-25 22:25 Abhishek Shrivastav
2009-05-26 13:54 ` Ira Rosen [this message]
     [not found] <4f5553710905310644y22561aa5s4b8482990360842e@mail.gmail.com>
2009-06-02 12:15 ` Ira Rosen

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=OF22C16181.5F6FF996-ONC22575C2.0043892B-C22575C2.0044711F@il.ibm.com \
    --to=irar@il.ibm.com \
    --cc=abhishek.shrivastav24@gmail.com \
    --cc=gcc@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).