Faster asin() was hiding in plain sight
1–10 of 140 posts
Re: Faster asin() was hiding in plain sight
#2Re: Faster asin() was hiding in plain sight
#3Re: Faster asin() was hiding in plain sight
#4I like throwing away work I've done. Frees up my mental capacity for other work to throw away.
Re: Faster asin() was hiding in plain sight
#5Re: Faster asin() was hiding in plain sight
#6Re: Faster asin() was hiding in plain sight
#7Re: Faster asin() was hiding in plain sight
#8They could be orthogonal improvements, but if I were prioritizing, I'd go for SIMD first.
I searched for asin on Intel's intrinsics guide. They have a AVX-512 instrinsic `_mm512_asin_ps` but it says "sequence" rather than single-instruction. Presumably the actual sequence they use is in some header file somewhere, but I don't know off-hand where to look, so I don't know how it compares to a SIMDified version of `fast_asin_cg`.
https://www.intel.com/content/www/us/en/docs/intrinsics-guid...
Re: Faster asin() was hiding in plain sight
#9Did some quick calculations, and at this precision, it seems a table lookup might be able to fit in the L1 cache depending on the CPU model.
Re: Faster asin() was hiding in plain sight
#10Isn't the faster approach SIMD [edit: or GPU]? A 1.05x to 1.90x speedup is great. A 16x speedup is better! They could be orthogonal improvements, but if I were prioritizing, I'd go for SIMD first. I searched for asin on Intel's intrinsics guide. They have a AVX-512 instrinsic `_mm512_asin_ps` but it says "sequence" rather than single-instruction. Presumably the actual sequence they use is in some header file somewher…