public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ira Rosen <IRAR@il.ibm.com>
To: Richard Sandiford <richard.sandiford@linaro.org>
Cc: gcc-patches@gcc.gnu.org, patches@linaro.org
Subject: Re: [3/9] STMT_VINFO_RELATED_STMT handling in vectorizable_store
Date: Sun, 17 Apr 2011 10:25:00 -0000	[thread overview]
Message-ID: <OF10FE96BC.623FAAA5-ONC2257875.00336E91-C2257875.0038910B@il.ibm.com> (raw)
In-Reply-To: <g4d3krfv2p.fsf@linaro.org>



gcc-patches-owner@gcc.gnu.org wrote on 12/04/2011 04:38:54 PM:

> vectorizable_store contains the code:
>
>   for (j = 0; j < ncopies; j++)
>     {
>       for (i = 0; i < vec_num; i++)
>    {
>      ...
>          if (j == 0)
>            STMT_VINFO_VEC_STMT (stmt_info) = *vec_stmt = new_stmt;
>          else
>            STMT_VINFO_RELATED_STMT (prev_stmt_info) = new_stmt;
>          prev_stmt_info = vinfo_for_stmt (new_stmt);
>          }
>     }
>
> That is, STMT_VINFO_VEC_STMT (stmt_info) and *vec_stmt contain the last
> statement emitted for the _last_ vector of the first copy.  However,
> for later copies, the last statement for _every_ vector is chained using
> STMT_VINFO_RELATED_STMT.  This seems a bit inconsistent, and isn't
> what I expected from the comments.  It also seems different from
> other vectorisation functions, where each copy has exactly one
> STMT_VINFO_RELATED_STMT.  I wasn't sure whether the difference here
> was deliberate or not.

I think it doesn't really matter because STMT_VINFO_RELATED_STMT is used
for retrieving copies of vector operands, and stores don't define any.

>
> The reason I'm changing it is that it makes the control flow for
> the new code more obvious.
>
> Tested on x86_64-linux-gnu and arm-linux-gnueabi.  OK to install?

OK.

Thanks,
Ira

>
> Richard
>
>
> gcc/
>    * tree-vect-stmts.c (vectorizable_store): Only chain one related
>    statement per copy.
>
> Index: gcc/tree-vect-stmts.c
> ===================================================================
> --- gcc/tree-vect-stmts.c   2011-04-12 11:55:08.000000000 +0100
> +++ gcc/tree-vect-stmts.c   2011-04-12 11:55:09.000000000 +0100
> @@ -3612,6 +3612,7 @@ vectorizable_store (gimple stmt, gimple_
>
>        if (1)
>     {
> +     new_stmt = NULL;
>       if (strided_store)
>         {
>           result_chain = VEC_alloc (tree, heap, group_size);
> @@ -3669,17 +3670,19 @@ vectorizable_store (gimple stmt, gimple_
>           if (slp)
>        continue;
>
> -         if (j == 0)
> -      STMT_VINFO_VEC_STMT (stmt_info) = *vec_stmt =  new_stmt;
> -         else
> -      STMT_VINFO_RELATED_STMT (prev_stmt_info) = new_stmt;
> -
> -         prev_stmt_info = vinfo_for_stmt (new_stmt);
>           next_stmt = DR_GROUP_NEXT_DR (vinfo_for_stmt (next_stmt));
>           if (!next_stmt)
>        break;
>         }
>     }
> +      if (!slp)
> +   {
> +     if (j == 0)
> +       STMT_VINFO_VEC_STMT (stmt_info) = *vec_stmt =  new_stmt;
> +     else
> +       STMT_VINFO_RELATED_STMT (prev_stmt_info) = new_stmt;
> +     prev_stmt_info = vinfo_for_stmt (new_stmt);
> +   }
>      }
>
>    VEC_free (tree, heap, dr_chain);

  reply	other threads:[~2011-04-17 10:18 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-12 13:21 [0/9] Direct support for loads and stores of interleaved vectors Richard Sandiford
2011-04-12 13:25 ` [1/9] Generalise vect_create_data_ref_ptr Richard Sandiford
2011-04-12 13:30   ` Richard Guenther
2011-04-12 13:28 ` [2/9] Reindent parts of vectorizable_load and vectorizable_store Richard Sandiford
2011-04-12 13:33   ` Richard Guenther
2011-04-12 14:39     ` Richard Sandiford
2011-04-12 13:40 ` [3/9] STMT_VINFO_RELATED_STMT handling in vectorizable_store Richard Sandiford
2011-04-17 10:25   ` Ira Rosen [this message]
2011-04-12 13:44 ` [4/9] Move power-of-two checks for interleaving Richard Sandiford
2011-04-12 13:57   ` Richard Guenther
2011-04-12 13:59 ` [5/9] Main target-independent support for direct interleaving Richard Sandiford
2011-04-17 14:26   ` Ira Rosen
2011-04-18 11:54   ` Richard Guenther
2011-04-18 11:57     ` Richard Sandiford
2011-04-18 12:54       ` Richard Guenther
2011-04-18 12:58         ` Richard Sandiford
2011-04-18 13:22           ` Richard Guenther
2011-04-12 14:01 ` [6/9] NEON vec_load_lanes and vec_store_lanes patterns Richard Sandiford
2011-04-15 13:20   ` Richard Earnshaw
2011-04-12 14:14 ` [7/9] Testsuite: remove vect_{extract_even_odd,strided}_wide Richard Sandiford
2011-04-15 12:43   ` Richard Guenther
2011-04-12 14:19 ` [8/9] Testsuite: split tests for strided accesses Richard Sandiford
2011-04-15 12:44   ` Richard Guenther
2011-04-12 14:29 ` [9/9] Testsuite: Replace vect_strided with vect_stridedN Richard Sandiford
2011-04-15 12:44   ` Richard Guenther
2011-04-12 14:34 ` [10/9] Add tests for stride-3 accesses Richard Sandiford
2011-04-15 12:45   ` Richard Guenther

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=OF10FE96BC.623FAAA5-ONC2257875.00336E91-C2257875.0038910B@il.ibm.com \
    --to=irar@il.ibm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=patches@linaro.org \
    --cc=richard.sandiford@linaro.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).