You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A lot of the SIMD tests run the same floats through all of the lanes, instead of just assuming lanewise operations to be implemented in a lanewise way. Is there any particular reason to do it this way? You could probably cut down the size of the tests by a factor of 2 or 4 if you just assumed all the lanes behave the same.
The text was updated successfully, but these errors were encountered:
Is speed a constraint for running tests? For operations that don't map to a single hardware instruction, or for engines that scalarize, testing all lanes could still be helpful in catching implementation bugs.
A lot of the SIMD tests run the same floats through all of the lanes, instead of just assuming lanewise operations to be implemented in a lanewise way. Is there any particular reason to do it this way? You could probably cut down the size of the tests by a factor of 2 or 4 if you just assumed all the lanes behave the same.
The text was updated successfully, but these errors were encountered: