public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alan Lawrence <alan.lawrence@arm.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	 Richard Biener <rguenther@suse.de>
Subject: Re: [testsuite] Don't xfail gcc.dg/vect/no-scevccp-outer-11.c
Date: Tue, 01 Sep 2015 12:53:00 -0000	[thread overview]
Message-ID: <55E59FAB.6030303@arm.com> (raw)
In-Reply-To: <yddwpwaiams.fsf@lokon.CeBiTec.Uni-Bielefeld.DE>

Rainer Orth wrote:
> It seems that since 20150717, gcc.dg/vect/no-scevccp-outer-11.c XPASSes
> everywhere:
> 
> XPASS: gcc.dg/vect/no-scevccp-outer-11.c scan-tree-dump-times vect "OUTER LOOP VECTORIZED." 1
> 
> To reduce testsuite noise, I'd like to remove the xfail as follows.
> Tested with the appropriate runtest invocations on i386-pc-solaris2.12
> and x86_64-unknown-linux-gnu.

I can confirm that this is also passing on aarch64 and arm.

Cheers, Alan

  reply	other threads:[~2015-09-01 12:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-01 12:31 Rainer Orth
2015-09-01 12:53 ` Alan Lawrence [this message]
2015-09-01 13:27 ` Richard Biener
2015-09-01 13:52   ` Rainer Orth

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=55E59FAB.6030303@arm.com \
    --to=alan.lawrence@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rguenther@suse.de \
    --cc=ro@CeBiTec.Uni-Bielefeld.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).