public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Yuri Rumyantsev <ysrumyan@gmail.com>
Cc: Richard Biener <richard.guenther@gmail.com>,
	gcc-patches <gcc-patches@gcc.gnu.org>,
		Igor Zamyatin <izamyatin@gmail.com>,
	Kirill Yukhin <kirill.Yukhin@gmail.com>
Subject: Re: [PATCH PR68542]
Date: Fri, 22 Jan 2016 14:50:00 -0000	[thread overview]
Message-ID: <CAMe9rOqX_79EVER8jdUBwNeAzMY=XE4fyK2sbq_QMLLr_0z88Q@mail.gmail.com> (raw)
In-Reply-To: <CAEoMCqSbNAZkTA-pJcuyce7=BotmGEBuMhWvHTqvNAn8kmDggw@mail.gmail.com>

On Fri, Jan 22, 2016 at 6:29 AM, Yuri Rumyantsev <ysrumyan@gmail.com> wrote:
> Richard,
>
> I fixed all remarks pointed by you in vectorizer part of patch. Could
> you take a look on modified patch.
>
> Uros,
>
> Could you please review i386 part of patch related to support of
> conditional branches with vector comparison.
>
> Bootstrap and regression testing did not show any new failures.
> Is it OK for trunk?
>
> Thanks.
> Yuri.
>
> ChangeLog:
>
> 2016-01-22  Yuri Rumyantsev  <ysrumyan@gmail.com>
>
> PR middle-end/68542
> * config/i386/i386.c (ix86_expand_branch): Add support for conditional
> brnach with vector comparison.
  ^^^^^^^^^ Typo.
> * config/i386/sse.md (define_expand "cbranch<mode>4): Add define-expand
> for vector comparion with eq/ne only.
> (optimize_mask_stores): New function.
> * tree-vect-stmts.c (vectorizable_mask_load_store): Initialize
> has_mask_store field of vect_info.
> * tree-vectorizer.c (vectorize_loops): Invoke optimaze_mask_stores for
> vectorized loops having masked stores after vec_info destroy.
> * tree-vectorizer.h (loop_vec_info): Add new has_mask_store field and
> correspondent macros.
> (optimize_mask_stores): Add prototype.
>
> gcc/testsuite/ChangeLog:
> * gcc.dg/vect/vect-mask-store-move-1.c: New test.
> * testsuite/gcc.target/i386/avx2-vect-mask-store-move1.c: New test.
>


-- 
H.J.

  reply	other threads:[~2016-01-22 14:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-30 13:24 Yuri Rumyantsev
2015-12-04 12:18 ` Richard Biener
2015-12-04 15:07   ` Yuri Rumyantsev
2015-12-07 10:57     ` Yuri Rumyantsev
2015-12-08 12:34       ` Yuri Rumyantsev
2015-12-10 13:36     ` Richard Biener
2015-12-11 14:03       ` Yuri Rumyantsev
2015-12-16 13:37         ` Richard Biener
2015-12-18 10:20           ` Yuri Rumyantsev
2016-01-11 10:06             ` Yuri Rumyantsev
2016-01-18 12:44               ` Richard Biener
2016-01-18 14:02                 ` Yuri Rumyantsev
2016-01-18 14:07                   ` Richard Biener
2016-01-18 14:50                     ` Yuri Rumyantsev
2016-01-20 12:25                       ` Richard Biener
2016-01-22 14:29                         ` Yuri Rumyantsev
2016-01-22 14:50                           ` H.J. Lu [this message]
2016-01-28 13:26                           ` Richard Biener
2016-01-28 13:37                             ` Yuri Rumyantsev
2016-01-28 14:24                               ` Uros Bizjak

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='CAMe9rOqX_79EVER8jdUBwNeAzMY=XE4fyK2sbq_QMLLr_0z88Q@mail.gmail.com' \
    --to=hjl.tools@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=izamyatin@gmail.com \
    --cc=kirill.Yukhin@gmail.com \
    --cc=richard.guenther@gmail.com \
    --cc=ysrumyan@gmail.com \
    /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).