I agree that a potential inconsistent experience is a problem, but I
disagree that SIMD would be the root of the problem, or even be a
significant contributor to it.
The problem is essentially: "How can we be sure that all compilers will
generate good code on all platforms?" As you said, we have a
Hi,
> - We submit a grant [3]. I believe James & co. do this
> (this is step 3/4 in [1]) - is this correct, @Kou?
> (Since you recently handled Julia.) And then we commit a
> tarball in the incubator drop area (though, I don't
> quite see how to do this, need to dig around)
Oh, I didn't d
I'm +1 for "arrow compute engine". In the docs we currently refer to
it as the "streaming execution engine". I do like the word
"streaming" as it is the difference between the engine and the general
"compute" module but the word is also overloaded and we can easily
include the word "streaming" in
Le 31/03/2022 à 09:19, Sasha Krassovsky a écrit :
As I showed, those auto-vectorized kernels may be vectorized only in some
situations, depending on the compiler version, the input datatypes...
I would more than anything interpret the fact that that code was vectorized at
all as an amazing
> As I showed, those auto-vectorized kernels may be vectorized only in some
> situations, depending on the compiler version, the input datatypes...
I would more than anything interpret the fact that that code was vectorized at
all as an amazing win for compiler technology, as it’s a very abstrac
