search for: vec_typ

...ing more. I?m planning on submitting vctrs to CRAN in the near future, but it?s very much a 0.1.0 release and I expect it to continue to evolve as more people try it out and give me feedback. I?d love to hear your thoughts\! vctrs has three main goals: - To define and motivate `vec_size()` and `vec_type()` as alternatives to `length()` and `class()`. - To define type- and size-stability, useful tools for analysing function interfaces. - To make it easier to create new S3 vector classes. ## Size and prototype `vec_size()` was motivated by my desire to have a function that captures...

...would be to start by creating a header file that implements the NEON intrinsics in terms of generic functionality and the Altivec ones. The header file would need to look kind of like this: #if defined(__powerpc__) || defined(__ppc__) #define neon_intrinsic1 ppc_neon_intrinsic1 static __inline__ vec_type __attribute__((__always_inline__, __nodebug__)) ppc_neon_intrinsic1(vec_type a1, vec_type a2) { ... } ... #endif If you look in tools/clang/lib/Headers you'll see lots of example intrinsics header files, and if you look in your build directory in tools/clang/lib/Headers you'll find th...

On 2 October 2013 12:17, Renato Golin <renato.golin at linaro.org> wrote: > On 2 October 2013 10:12, Steven Newbury <steve at snewbury.org.uk> wrote: > >> How does this make any sense? >> > > I have to agree with you that this doesn't make much sense, but there is a > case where you would want something like that: when the original source > uses NEON

On 2 October 2013 10:12, Steven Newbury <steve at snewbury.org.uk> wrote: > How does this make any sense? > I have to agree with you that this doesn't make much sense, but there is a case where you would want something like that: when the original source uses NEON intrinsics, and there is no alternative in AltiVec, AVX or even plain C. We encourage people to use NEON intrinsics,

...k these are good principles because they makes types simpler to understand and to implement. Method dispatch for `vec_c()` is quite simple because associativity and commutativity mean that we can determine the output type only by considering a pair of inputs at a time. To this end, vctrs provides `vec_type2()` which takes two inputs and returns their common type (represented as zero length vector): str(vec_type2(integer(), double())) #> num(0) str(vec_type2(factor("a"), factor("b"))) #> Factor w/ 2 levels "a","b": # NB: not all t...

...ecause they makes types simpler to understand and to > implement. > > Method dispatch for `vec_c()` is quite simple because associativity and > commutativity mean that we can determine the output type only by > considering a pair of inputs at a time. To this end, vctrs provides > `vec_type2()` which takes two inputs and returns their common type > (represented as zero length vector): > > str(vec_type2(integer(), double())) > #> num(0) > > str(vec_type2(factor("a"), factor("b"))) > #> Factor w/ 2 levels "a",&q...

...at < > + (int_AMDGPU_pow rc:$src0, rc:$src1), > + (exp_ieee (mul rc:$src1, (log_ieee rc:$src0))) > +>; > + > +/* Other helper patterns */ > +/* --------------------- */ > + > +/* Extract element pattern */ > +class Extract_Element <ValueType sub_type, ValueType vec_type, > + RegisterClass vec_class, int sub_idx, > + SubRegIndex sub_reg>: Pat< > + (sub_type (vector_extract (vec_type vec_class:$src), sub_idx)), > + (EXTRACT_SUBREG vec_class:$src, sub_reg) > +>; > + > +/* Insert element pattern...