From: Ira Rosen <ira.rosen@linaro.org>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Richard Guenther <rguenther@suse.de>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] SLP vectorize calls (take 2)
Date: Tue, 08 Nov 2011 08:22:00 -0000 [thread overview]
Message-ID: <CAKSNEw45bo3HhnAuarTJpW5KMo4K_5H1HjX8gDKneL1yrC_OtA@mail.gmail.com> (raw)
In-Reply-To: <20111108072254.GB17997@tyan-ft48-01.lab.bos.redhat.com>
On 8 November 2011 09:22, Jakub Jelinek <jakub@redhat.com> wrote:
> First of all, whether copysignf, sqrtf and/or lrint are vectorized is
> very much target specific, should I guard the dg-final lines with
> { target { i?86-*-* x86_64-*-* } }
> resp.
> { target { { i?86-*-* x86_64-*-* } && !lp64 } }
> (the latter for lrint - we don't vectorize it on x86_64), or add
> vect_call_copysignf, vect_call_sqrtf, vect_call_lrint tests in *.exp?
The second option would be nicer.
>
> For the split, some fns are hybrid, so shall I split f1+f2+f3 as slp
> and f4 as loop, or is f3 (hybrid) something else?
> What test names
> should I use? fast-math-slp-call-*.c/fast-math-vect-call-*.c or something
> else? From what I gather for bb slp the test should start with bb-slp-*
> (is that f1/f2 or just f1?), but then there is currently no way to
> add -ffast-math.
In fast-math-vect-call-1.c, f1 is basic block SLP, f2+f3 are loop SLP,
and f4 is regular loop vectorization.
So, f1 should be in fast-math-bb-slp-call-1.c, with
/* { dg-final { scan-tree-dump-times "basic block vectorized using
SLP" 1 "slp" } } */
/* { dg-final { cleanup-tree-dump "slp" } } */
and
# -ffast-math
set VECT_SLP_CFLAGS $SAVED_VECT_SLP_CFLAGS
lappend VECT_SLP_CFLAGS "-ffast-math"
dg-runtest [lsort [glob -nocomplain
$srcdir/$subdir/fast-math-bb-slp-*.\[cS\]]] \
"" $VECT_SLP_CFLAGS
in vect.exp.
The rest can simply stay in fast-math-vect-call-1.c, but to check SLP please use
/* { dg-final { scan-tree-dump-times "vectorized 1 loops" X "vect" } } */
/* { dg-final { scan-tree-dump-times "vectorizing stmts using SLP" Y
"vect" } } */
/* { dg-final { cleanup-tree-dump "vect" } } */
>
>> Also there is no need in dg-do run.
>
> You mean because it is the default?
Yes.
Thanks,
Ira
> Certainly it is useful to test
> that gcc doesn't miscompile the tests.
>
> Jakub
>
next prev parent reply other threads:[~2011-11-08 8:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-20 23:56 [RFC PATCH] SLP vectorize calls Jakub Jelinek
2011-10-21 12:45 ` Ira Rosen
2011-10-21 13:31 ` Jakub Jelinek
2011-10-21 14:26 ` Ira Rosen
2011-10-21 14:42 ` Jakub Jelinek
2011-10-21 15:51 ` Ira Rosen
2011-11-07 18:44 ` [PATCH] SLP vectorize calls (take 2) Jakub Jelinek
2011-11-08 8:00 ` Ira Rosen
2011-11-08 8:03 ` Jakub Jelinek
2011-11-08 8:22 ` Ira Rosen [this message]
2011-11-08 10:03 ` [PATCH] SLP vectorize calls (take 3) Jakub Jelinek
2011-11-08 10:15 ` Ira Rosen
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=CAKSNEw45bo3HhnAuarTJpW5KMo4K_5H1HjX8gDKneL1yrC_OtA@mail.gmail.com \
--to=ira.rosen@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.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).