public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: James Greenhalgh <james.greenhalgh@arm.com>
To: Yuri Rumyantsev <ysrumyan@gmail.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
	nd@arm.com, "Richard Biener" <richard.guenther@gmail.com>,
	"Uros Bizjak" <ubizjak@gmail.com>,
	"Илья Энкович" <enkovich.gnu@gmail.com>,
	"Igor Zamyatin" <izamyatin@gmail.com>
Subject: Re: [Patch] Gate vect-mask-store-move-1.c correctly, and actually output the dump
Date: Mon, 08 Feb 2016 13:40:00 -0000	[thread overview]
Message-ID: <20160208134024.GA19031@arm.com> (raw)
In-Reply-To: <CAEoMCqTGFs71QaJYof96ix=v_AOUmf=TLEs4hMa3LmDhUOjJ4w@mail.gmail.com>

On Mon, Feb 08, 2016 at 04:29:31PM +0300, Yuri Rumyantsev wrote:
> Hi James,
> 
> Thanks for reporting this issue.
> I prepared slightly different patch since we don't need to add
> tree-vect dump option - it is on by default for all tests in /vect
> directory.

Hm, I added that line as my test runs were showing:

  UNRESOLVED: gcc.dg/vect/vect-mask-store-move-1.c: dump file does not exist

I would guess the explicit 

  /* { dg-options "-O3" } */

is clobbering the vect.exp setup of flags?

This also affects the x86-64 results H.J. Lu is sending out:

  https://gcc.gnu.org/ml/gcc-testresults/2016-02/msg00824.html

Thanks,
James

> 
> gcc/testsuite/ChangeLog:
> 
> * gcc.dg/vect/vect-mask-store-move-1.c: Gate dump with x86 target.
> 
> 2016-02-08 16:07 GMT+03:00 James Greenhalgh <james.greenhalgh@arm.com>:
> >
> > Hi,
> >
> > As far as I can tell, this testcase will only vectorize for x86_64/i?86
> > targets, so it should be gated to only check for vectorization on those.
> >
> > Additionally, this test wants to scan the vectorizer dumps, so we ought
> > to add -fdump-tree-vect-all to the options.
> >
> > Checked on aarch64 (cross/native) and x86 with no issues.
> >
> > OK?
> >
> > Thanks,
> > James
> >
> > ---
> > 2016-02-08  James Greenhalgh  <james.greenhalgh@arm.com>
> >
> >         * gcc.dg/vect/vect-mask-store-move-1.c: Add dump option, and gate
> >         check on x86_64/i?86.
> >


  reply	other threads:[~2016-02-08 13:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAFULd4ZVSDCEyyeT7fdF1Jccch3RjkkOZYsfzhxC_Ze9YuaYnA@mail.gmail.com>
     [not found] ` <CAEoMCqSWx2AKqmzQYpm880BG0YsAtV2MmF1aVsSrJ-Oy+Dq7Jw@mail.gmail.com>
     [not found]   ` <CAFULd4bA1f085BsrPO87gX3iw34dVjvF2Rz5DA=r2E66TywuJQ@mail.gmail.com>
2016-01-29 14:13     ` [off-list] Re: [PATCH PR68542] Yuri Rumyantsev
2016-01-29 15:48       ` Uros Bizjak
2016-02-08 13:07       ` [Patch] Gate vect-mask-store-move-1.c correctly, and actually output the dump James Greenhalgh
2016-02-08 13:29         ` Yuri Rumyantsev
2016-02-08 13:40           ` James Greenhalgh [this message]
2016-02-08 14:23             ` Yuri Rumyantsev
2016-02-08 14:24             ` Richard Biener
2016-02-09 11:25               ` James Greenhalgh
2016-02-09 11:26                 ` Richard Biener
2016-02-09 11:29                 ` Jakub Jelinek
2016-02-08 16:08         ` Jeff Law

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=20160208134024.GA19031@arm.com \
    --to=james.greenhalgh@arm.com \
    --cc=enkovich.gnu@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=izamyatin@gmail.com \
    --cc=nd@arm.com \
    --cc=richard.guenther@gmail.com \
    --cc=ubizjak@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).