Re: [C++] Replacing xsimd with compiler autovectorization

2022-03-30 Thread Sasha Krassovsky
Yep a suffix _simd would make perfect sense too. Sasha > 30 марта 2022 г., в 22:58, Micah Kornfield написал(а): > >  >> >> >> As for a naming convention, we could use something like the prefix `simd_`? > > Bikeshedding moment: we use suffixes today for instructions sets would it > make se

Re: [C++] Replacing xsimd with compiler autovectorization

2022-03-30 Thread Antoine Pitrou
Le 31/03/2022 à 01:24, Weston Pace a écrit : Apologies if this is an over simplified opinion but does it have to be one or the other? If people contribute and maintain XSIMD kernels then great. If people contribute and maintain auto-vectorizable kernels then great. Then it just comes down to

Re: [C++] Replacing xsimd with compiler autovectorization

2022-03-30 Thread Micah Kornfield
> > As for a naming convention, we could use something like the prefix `simd_`? Bikeshedding moment: we use suffixes today for instructions sets would it make sense to continue that for consistency. `scalar_arithmetic_simd.cc`? On Wed, Mar 30, 2022 at 4:58 PM Sasha Krassovsky wrote: > Yep, tha

Re: Arrow sync call March 30 at 12:00 US/Eastern, 16:00 UTC

2022-03-30 Thread Ian Cook
Attendees: Ian Cook James Duong Ian Joiner Micah Kornfield David Li Rok Mihevc Matt Topol Discussion: C++ helpers for conversion between Arrow columnar formats and row-oriented formats - Discussion at [1]; comments requested - Could this be pursued by factoring out existing code from the CSV

Help drafting Apache Arrow 2022-04 board report

2022-03-30 Thread Sutou Kouhei
Hi, I started a document where we can crowdsource the 2022-04 board report: https://github.com/apache/arrow/pull/12759 (We used Goolge Docs before but I want to try pull request this time.) If you're a committer, you can push your changes directly. Others can leave comments/suggestions. It's

Re: [C++] Replacing xsimd with compiler autovectorization

2022-03-30 Thread Sasha Krassovsky
Yep, that's basically what I'm suggesting. If someone contributes an xsimd kernel that's faster than the autovectorized kernel, then it'll be seamless to switch. The xsimd and autovectorized kernels would share the same source file, so anyone contributing an xsimd kernel would just have to change t

Re: [C++] Replacing xsimd with compiler autovectorization

2022-03-30 Thread Weston Pace
Apologies if this is an over simplified opinion but does it have to be one or the other? If people contribute and maintain XSIMD kernels then great. If people contribute and maintain auto-vectorizable kernels then great. Then it just comes down to having consistent dispatch rules. Something lik

Re: [Flight][Java][JDBC] IP clearance of Flight JDBC Driver

2022-03-30 Thread David Li
So the process is at [1]. I think the following needs to happen: - James, can you create a PR with the current state of the driver, but targeted against the `flight-sql-jdbc` branch [2]? Please make sure to update files to have the Apache license preamble. We'll use this as the subject of the

Re: [C++] Replacing xsimd with compiler autovectorization

2022-03-30 Thread Micah Kornfield
> > We were not going to use xsimd's dynamic dispatch, and instead roll our own There is already a dynamic dispatch facility see: arrow/util/dispatch.h Since we're rolling our own dynamic dispatch, we'd still have to compile > the same source file several times with different, so my proposal does

[Flight][Java][JDBC] IP clearance of Flight JDBC Driver

2022-03-30 Thread James Duong
Following up on today's sync-up: We're looking to start IP clearance of the JDBC driver in https://github.com/apache/arrow/pull/12254 I believe we discussed merging the PR into a branch to start the process. What else is involved in this process? -- *James Duong* Lead Software Developer Bit Qu

Re: [C++] Replacing xsimd with compiler autovectorization

2022-03-30 Thread Sasha Krassovsky
> Looking at the disassembly, the int16 and int32 versions are unrolled and vectorized by clang 12.0, the int8 and int64 are not... I think a big part of this is how fragile the current kernel system implementation is. It seems to rely on templating lots of different parts of kernels and hoping com

Arrow sync call March 30 at 12:00 US/Eastern, 16:00 UTC

2022-03-30 Thread Ian Cook
Hi all, Our biweekly sync call is today at 12:00 noon Eastern time. The Zoom meeting URL for this and other biweekly Arrow sync calls is: https://zoom.us/j/87649033008?pwd=SitsRHluQStlREM0TjJVYkRibVZsUT09 Alternatively, enter this information into the Zoom website or app to join the call: Meetin

Re: [C++] Replacing xsimd with compiler autovectorization

2022-03-30 Thread Johan Mabille
Hi all, xsimd core developer here writing on behalf of the xsimd core team ;) I just wanted to add some elements to this thread: - xsimd is more than a library that wraps simple intrinsics. It provides vectorized (and accurate) implementations of the traditional mathematical functions (exp, sin,

Re: [C++] Replacing xsimd with compiler autovectorization

2022-03-30 Thread Antoine Pitrou
Hi Sasha, Le 30/03/2022 à 00:14, Sasha Krassovsky a écrit : I've noticed that we include xsimd as an abstraction over all of the simd architectures. I'd like to propose a different solution which would result in fewer lines of code, while being more readable. My thinking is that anything simp