public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tamar Christina <Tamar.Christina@arm.com>
To: Richard Biener <rguenther@suse.de>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>, nd <nd@arm.com>
Subject: RE: [PATCH][GCC][SLP][testsuite] Turn off vect-epilogue-nomask for slp-rect-3
Date: Thu, 28 Nov 2019 22:11:00 -0000	[thread overview]
Message-ID: <DB6PR0802MB2309CB7CEC1DF214D9075C8BFF470@DB6PR0802MB2309.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <nycvar.YFH.7.76.1911282021300.5566@zhemvz.fhfr.qr>

Hi Richi,

> >
> > This patch turns off vect-epilogue-nomask for slp-reduc-3 as it seems
> > that the epiloque in this loop is vectorizable using SLP and smaller
> > VF.  Since this test expects there to be no SLP vectorization at all
> > the testcase then fails for arm targets.
> 
> Actually we do expect SLP vectorization, just the counting might go wrong.
> 
> What's the actual FAIL for arm?

I should have worded this better considering the testcase literally contains SLP in the name...

The failure is for the XFAIL 

/* { dg-final { scan-tree-dump-times "vectorizing stmts using SLP" 1 "vect" { xfail { vect_widen_sum_hi_to_si_pattern || { ! vect_unpack } } } } } */

And my understanding as to what is happening is that without epiloque no mask it would only try HI modes, but thanks to the epiloques nomask
It tries QI mode as well which succeeds.  The xfail then generates an xpass since the condition on it checks for HI to SI and not QI.

So I disabled the epiloque mask since it seems to violate the conditions the test actually wanted to test for.

Not quite sure why it's failing only on Arm though.

Regards,
Tamar

> 
> Disabling epilogue vect is of course OK if it simplifies things.
> 
> > Regtested on arm-none-eabi and no issues.
> >
> > Ok for trunk?
> 
> > Thanks,
> > Tamar
> >
> > gcc/testsuite/ChangeLog:
> >
> > 2019-11-28  Tamar Christina  <tamar.christina@arm.com>
> >
> > 	* gcc.dg/vect/slp-reduc-3.c: Turn off epilogue-nomask.
> >
> >
> 
> --
> Richard Biener <rguenther@suse.de>
> SUSE Software Solutions Germany GmbH, Maxfeldstrasse 5, 90409
> Nuernberg, Germany; GF: Felix Imendörffer; HRB 36809 (AG Nuernberg)

  reply	other threads:[~2019-11-28 21:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-28 17:32 Tamar Christina
2019-11-28 19:41 ` Richard Biener
2019-11-28 22:11   ` Tamar Christina [this message]
2019-11-29  8:41     ` Richard Biener

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=DB6PR0802MB2309CB7CEC1DF214D9075C8BFF470@DB6PR0802MB2309.eurprd08.prod.outlook.com \
    --to=tamar.christina@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=nd@arm.com \
    --cc=rguenther@suse.de \
    /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).