From: Steve Ellcey <sje@cup.hp.com>
To: Ira Rosen <IRAR@il.ibm.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [patch, testsuite] Fix vectorizer testsuite failures on ARM
Date: Thu, 16 Jun 2011 16:26:00 -0000 [thread overview]
Message-ID: <1308240839.10986.93.camel@hpsje.cup.hp.com> (raw)
In-Reply-To: <OFA1A767B4.F0F36C45-ONC22578B1.001FAF40-C22578B1.001FEF1C@il.ibm.com>
On Thu, 2011-06-16 at 08:48 +0300, Ira Rosen wrote:
> > 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
I went ahead and created a bug report (PR 49443) and added the dump file
to that report as an attachment.
Steve Ellcey
sje@cup.hp.com
prev parent reply other threads:[~2011-06-16 16:14 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
2011-06-16 16:26 ` Steve Ellcey [this message]
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=1308240839.10986.93.camel@hpsje.cup.hp.com \
--to=sje@cup.hp.com \
--cc=IRAR@il.ibm.com \
--cc=gcc-patches@gcc.gnu.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).