‐‐‐ Original Message ‐‐‐
On Thursday, March 5, 2020 6:59 PM, Segher Boessenkool
wrote:
> On Thu, Mar 05, 2020 at 05:04:16PM +0000, GT wrote:
>
> > 2. Multiple other testcases in testsuite/gcc.dg/vect/ have this line at
> > the top:
> > /* { dg-additional-
‐‐‐ Original Message ‐‐‐
On Thursday, March 5, 2020 6:59 PM, Segher Boessenkool
wrote:
> On Thu, Mar 05, 2020 at 05:04:16PM +0000, GT wrote:
>
> > At the top of that file is dejagnu directive:
> > /* { dg-require-effective-target vect_int } */
> >
> >
‐‐‐ Original Message ‐‐‐
On Thursday, March 5, 2020 6:59 PM, Segher Boessenkool
wrote:
> On Thu, Mar 05, 2020 at 05:04:16PM +0000, GT wrote:
>
> > At the top of that file is dejagnu directive:
> > /* { dg-require-effective-target vect_int } */
> >
> >
I tried the make command below:
make check RUNTESTFLAGS="*.exp=*simd*"
gcc.log did not have any output indicating that it ran
.../gcc/testsuite/gcc.dg/vect/vect-simd-2.c
At the top of that file is dejagnu directive:
/* { dg-require-effective-target vect_int } */
1. How do I check to see if vect
‐‐‐ Original Message ‐‐‐
On Wednesday, January 15, 2020 3:20 PM, GT wrote:
> ‐‐‐ Original Message ‐‐‐
> On Thursday, January 9, 2020 8:42 AM, Richard Biener
> richard.guent...@gmail.com wrote:
>
> > As for the other question for testing you probably want to
‐‐‐ Original Message ‐‐‐
On Thursday, January 9, 2020 8:42 AM, Richard Biener
wrote:
>
> As for the other question for testing you probably want to provide a
> OMP simd declaration
> of a function like
>
> _Complex double mycexpi (double);
>
> and make a testcase like
>
> void foo (_Comp
‐‐‐ Original Message ‐‐‐
On Monday, December 9, 2019 3:39 AM, Richard Biener
wrote:
> > I'm modifying the code trying to get complex double accepted as a valid
> > type by the vectorizer.
> > This is the first time I'm dealing with GCC source so I ask for some
> > patience.
> > Functio
‐‐‐ Original Message ‐‐‐
On Monday, December 9, 2019 3:39 AM, Richard Biener
wrote:
> You don't want to do it this way but map _Complex double to a vector
> of 2 * n doubles instead.
> Look into get_related_vectype_for_scalar_type where it alreday has
> code to "change" the
> scalar type
‐‐‐ Original Message ‐‐‐
On Monday, December 9, 2019 12:36 PM, GT wrote:
> ‐‐‐ Original Message ‐‐‐
> On Monday, December 9, 2019 3:39 AM, Richard Biener
> richard.guent...@gmail.com wrote:
>
> > > I'm modifying the code trying to get complex
‐‐‐ Original Message ‐‐‐
On Monday, December 9, 2019 3:39 AM, Richard Biener richard.guent...@gmail.com
wrote:
> > I'm modifying the code trying to get complex double accepted as a valid
> > type by the vectorizer.
> > This is the first time I'm dealing with GCC source so I ask for some
‐‐‐ Original Message ‐‐‐
On Friday, December 6, 2019 12:43 PM, Richard Biener richard.guent...@gmail.com
wrote:
...
...
> > Are we certain the change we want is to support _Complex double so that
> > cexpi is auto-vectorized?
> > Looking at the resulting executable of the code with sinco
‐‐‐ Original Message ‐‐‐
On Friday, December 6, 2019 6:38 AM, Richard Biener
wrote:
> On Fri, Dec 6, 2019 at 12:15 PM Jakub Jelinek ja...@redhat.com wrote:
>
> > On Fri, Dec 06, 2019 at 11:48:03AM +0100, Richard Biener wrote:
> >
> > > So I used
> > > void sincos(double x, double *sin, d
‐‐‐ Original Message ‐‐‐
On Thursday, December 5, 2019 4:44 AM, Richard Biener
wrote:
...
...
...
> >
> > I'm trying to identify the source code which needs modification but I need
> > help proceeding.
> > I am comparing two compilations: The first is a simple file with a call to
>
‐‐‐ Original Message ‐‐‐
On Wednesday, November 27, 2019 3:19 AM, Richard Biener
wrote:
...
> > Questions:
> >
> > 1. Should we aim to provide a vectorized version of __builtin_cexpi? If
> > so, it would have
> > to be a PPC64-only vector __builtin-cexpi, right?
> >
> > 2. Or sho
> >
> > i wonder if gcc can auto-vectorize scalar sincos
> > calls, the vectorizer seems to want the calls to
> > have no side-effect, but attribute pure or const
> > is not appropriate for sincos (which has no return
> > value but takes writable pointer args)
>
> We have __builtin_cexpi for that b
‐‐‐ Original Message ‐‐‐
On Monday, September 30, 2019 9:52 AM, Szabolcs Nagy
wrote:
> On 27/09/2019 20:23, GT wrote:
>
> > I am attempting to create a vector version of sincos for PPC64.
> > The relevant discussion thread is on the GLIBC libc-alpha mailing lis
I am attempting to create a vector version of sincos for PPC64.
The relevant discussion thread is on the GLIBC libc-alpha mailing list.
Navigate it beginning at
https://sourceware.org/ml/libc-alpha/2019-09/msg00334.html
The intention is to reuse as much as possible from the existing GCC
implemen
17 matches
Mail list logo
