Google removes SIMD.js support from Chromium

Re:Google removes SIMD.js support from Chromium by sddfd on Sunday June 04, 2017 @10:40AM (#14481802)

I get your point.

However, I don't think it is useful to consider a compiler to be a replacement for programmers. Compilers are tools for programmers. The more time a compiler saves a programmer, the better it is.

I think there is a middle ground between writing inline assembly and fully automatic vectorization that would be less time intensive than manual vectorization and more predictable and available earlier than fully automatic vectorization. I wonder what would have to be done to find it and provide support for it in GCC/LLVM.

[ Parent | on HN ]

Re:Google removes SIMD.js support from Chromium by corysama on Sunday June 04, 2017 @11:05AM (#14481919)

So... SIMD intrinsics?

You also need to take into account that a huge chunk of the work in SIMD is the need to rearrange your data to be more amenable to the CPU. C++ compilers are very restricted in what they can do for you there.

[ Parent | on HN ]