From: Christophe Lyon <christophe.lyon@linaro.org>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Ramana Radhakrishnan <ramana.gcc@googlemail.com>,
Richard Biener <rguenther@suse.de>,
Ilya Enkovich <enkovich.gnu@gmail.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fix SLP wrong-code with VECTOR_BOOLEAN_TYPE_P (PR tree-optimization/71259)
Date: Tue, 07 Jun 2016 12:43:00 -0000 [thread overview]
Message-ID: <CAKdteObZd0CzhVVwFU3whOjt2cMk1vHsdcpsKJ7Z0J3ot2Wr2g@mail.gmail.com> (raw)
In-Reply-To: <20160607094220.GP7387@tucnak.redhat.com>
On 7 June 2016 at 11:42, Jakub Jelinek <jakub@redhat.com> wrote:
> On Tue, Jun 07, 2016 at 10:36:25AM +0100, Ramana Radhakrishnan wrote:
>> On Tue, Jun 7, 2016 at 10:28 AM, Jakub Jelinek <jakub@redhat.com> wrote:
>> > On Tue, Jun 07, 2016 at 11:23:01AM +0200, Christophe Lyon wrote:
>> >> > --- gcc/testsuite/gcc.dg/vect/pr71259.c.jj 2016-06-03 17:05:37.693475438 +0200
>> >> > +++ gcc/testsuite/gcc.dg/vect/pr71259.c 2016-06-03 17:05:32.418544731 +0200
>> >> > @@ -0,0 +1,28 @@
>> >> > +/* PR tree-optimization/71259 */
>> >> > +/* { dg-do run } */
>> >> > +/* { dg-options "-O3" } */
>> >
>> > Would changing this from dg-options to dg-additional-options help for the
>> > ARM issues?
>> > check_vect () is the standard way for testing for HW vectorization support
>> > and hundreds of tests use it.
>>
>>
>> all tests in gcc.dg/vect have some form of dg-require-effective-target
>
> No, at least 170+ tests don't.
>
>> - so I think this test should just have dg-require-effective-target
>> "vect_int" .
>
> No, why? This test doesn't test whether the function has been vectorized.
> It only tests whether it works.
> And the check_vect () is supposed to exit early if some extra flags were
> passed by vect.exp (like e.g. on i?86-linux -msse2) and the HW doesn't
> support those.
>
But this makes the tests fails, rather than be unsupported, right?
> Jakub
next prev parent reply other threads:[~2016-06-07 12:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 17:13 [PATCH] Fix up my recent change to vect_get_constant_vectors (PR tree-optimization/69207) Jakub Jelinek
2016-01-12 14:21 ` Ilya Enkovich
2016-06-03 17:33 ` [PATCH] Fix SLP wrong-code with VECTOR_BOOLEAN_TYPE_P (PR tree-optimization/71259) Jakub Jelinek
2016-06-06 8:06 ` Richard Biener
2016-06-06 17:44 ` Jakub Jelinek
2016-06-07 7:13 ` Richard Biener
2016-06-07 9:23 ` Christophe Lyon
2016-06-07 9:28 ` Jakub Jelinek
2016-06-07 9:36 ` Ramana Radhakrishnan
2016-06-07 9:42 ` Jakub Jelinek
2016-06-07 12:43 ` Christophe Lyon [this message]
2016-06-07 12:47 ` Jakub Jelinek
2016-06-08 9:28 ` Christophe Lyon
2016-06-08 10:26 ` Richard Biener
2016-06-08 10:32 ` Jakub Jelinek
2016-06-08 10:33 ` Richard Biener
2016-06-08 14:44 ` Christophe Lyon
2016-06-08 14:50 ` Jakub Jelinek
2016-06-09 12:18 ` Christophe Lyon
2016-06-09 12:31 ` Jakub Jelinek
2016-06-09 12:40 ` Christophe Lyon
2016-06-09 12:46 ` Jakub Jelinek
2016-06-15 8:45 ` Christophe Lyon
2016-06-21 13:10 ` Christophe Lyon
2016-06-21 13:13 ` Jakub Jelinek
2016-06-21 13:46 ` Christophe Lyon
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=CAKdteObZd0CzhVVwFU3whOjt2cMk1vHsdcpsKJ7Z0J3ot2Wr2g@mail.gmail.com \
--to=christophe.lyon@linaro.org \
--cc=enkovich.gnu@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=ramana.gcc@googlemail.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).