public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ira Rosen <IRAR@il.ibm.com>
To: Steve Ellcey <sje@cup.hp.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [patch, testsuite] Fix vectorizer testsuite failures on ARM
Date: Thu, 16 Jun 2011 06:00:00 -0000	[thread overview]
Message-ID: <OFA1A767B4.F0F36C45-ONC22578B1.001FAF40-C22578B1.001FEF1C@il.ibm.com> (raw)
In-Reply-To: <201106151715.p5FHFRe20685@lucas.cup.hp.com>



Steve Ellcey <sje@cup.hp.com> wrote on 15/06/2011 08:15:27 PM:

>
> > 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.
>
> Ira,
>
> This change broke vect-peel-3.c and vect-peel-4.c on IA64 HP-UX.
> I get these failures:
>
>    FAIL: gcc.dg/vect/vect-peel-3.c -flto scan-tree-dump-times vect
> "Alignment of access forced using peeling" 1
>    FAIL: gcc.dg/vect/vect-peel-3.c -flto scan-tree-dump-times vect
> "vectorized 1 loops" 1
>    FAIL: gcc.dg/vect/vect-peel-3.c scan-tree-dump-times vect
> "Alignment of access forced using peeling" 1
>    FAIL: gcc.dg/vect/vect-peel-3.c scan-tree-dump-times vect
> "vectorized 1 loops" 1
>    FAIL: gcc.dg/vect/vect-peel-4.c -flto scan-tree-dump-times vect
> "vectorized 1 loops" 1
>    FAIL: gcc.dg/vect/vect-peel-4.c scan-tree-dump-times vect
> "vectorized 1 loops" 1
>
> I think that changing i+6 and i+2 to i+5 and i+1 broke things on HP-UX
> because we are big-endian and the old values may not have worked on ARM
> because it is little-endian (just guessing).
>
> I am not sure what we want to do to make this test work on both
platforms.
> Do you have any ideas?

I don't think it is related to endianess.
Could you please send me the dump files (created with
-fdump-tree-vect-details)?

Thanks,
Ira

>
> Steve Ellcey
> sje@cup.hp.com

  reply	other threads:[~2011-06-16  5:49 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
2011-06-15 17:30 ` Steve Ellcey
2011-06-16  6:00   ` Ira Rosen [this message]
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=OFA1A767B4.F0F36C45-ONC22578B1.001FAF40-C22578B1.001FEF1C@il.ibm.com \
    --to=irar@il.ibm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=sje@cup.hp.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).