search for: __vsinf

...o C++ (consistency?) 2) It seems your "x" prefix is probably safe, but more safe may be clg (like clgsinf) - This is a bit verbose of course, but I think you're trying to avoid a collision, right? If this library is meant only for internal compiler usage and not exposed, wouldn't __vsinf be really what makes sense? (If Apple or others use this it shouldn't be public facing) If there is meant to be a user facing API - maybe it could be exposed as an alias with a conflicting API, but not automatically used in the compiler.. This would mean there's both __vsinf (or xsinf if yo...

Hi everyone, I think that everyone is on the same page. We'll put together a patch for review. One remaining question: There seem two potential homes for this library: parallel_libs and compiler-rt. Opinions on where the vectorized math functions should live? My inclination is to target it for the new parallel_libs project, in part because I feel like compiler-rt has too many things grouped