public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ira Rosen <ira.rosen@linaro.org>
To: gcc-patches@gcc.gnu.org
Cc: Patch Tracking <patches@linaro.org>
Subject: Re: [patch, testsuite] Fix vectorizer testsuite failures on ARM
Date: Mon, 13 Jun 2011 09:22:00 -0000	[thread overview]
Message-ID: <BANLkTikyF15uFM2ZFFM3D94KHTnjW_-PkA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimb5zs8eCUCQ2eyZFw-d=FerEY9Wg@mail.gmail.com>

On 9 June 2011 13:00, Ira Rosen <ira.rosen@linaro.org> wrote:
> Hi,
>
> This patch fixes several vectorizer testsuite failures on ARM:
> - vect-16.c checks that the vectorization fails without -ffast-math,
> but -ffast-math is a default flag for vector tests on ARM. I renamed
> the test to no-fast-math-vect-16.c to avoid the use of the flag for
> it.
> - vect-peel-3.c and vect-peel-4.c test vectorizer's peeling heuristics
> ignoring double-word vectors. This patch changes the misalignment
> values of the data-refs.
> - bb-slp-10.c contains a misaligned store supported not only on
> vect_hw_misalign targets, but also on vect_element_align targets. The
> patch fixes that.
>
> Tested on arm-linux-gnueabi, powerpc64-suse-linux and x86_64-suse-linux.
> OK for mainline?
>

I'll commit this patch tomorrow if nobody objects.

Thanks,
Ira

> Thanks,
> Ira
>
> testsuite/ChangeLog:
>
>       * gcc.dg/vect/vect-16.c: Rename to ...
>       * gcc.dg/vect/no-fast-math-vect16.c: ... this.
>       * gcc.dg/vect/vect-peel-3.c: Adjust misalignment values
>       for double-word vectors.
>       * gcc.dg/vect/vect-peel-4.c: Likewise.
>       * gcc.dg/vect/bb-slp-10.c: Replace vect_hw_misalign with
>       vect_element_align.
>       * gcc.dg/vect/vect.exp: Run no-fast-math-* tests with
>       -fno-fast-math.
>

  reply	other threads:[~2011-06-13  7:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-09 10:07 Ira Rosen
2011-06-13  9:22 ` Ira Rosen [this message]
2011-06-15 17:30 ` Steve Ellcey
2011-06-16  6:00   ` Ira Rosen
2011-06-16 16:26     ` Steve Ellcey

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=BANLkTikyF15uFM2ZFFM3D94KHTnjW_-PkA@mail.gmail.com \
    --to=ira.rosen@linaro.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=patches@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).