Repository navigation
Fix: keep numpy buffer operations off the NEON vector path (macOS CI red since #270) - #291
Merged
Merged
Conversation
…per element (CI red since #270)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
#270's arm64 vector loop computed numpy-tainted F64 ops lane-wise without tp_np_f64, so no 'overflow encountered in scalar multiply' warning (test_division_matches_numpy, red on macOS CI). _vec_plan now requires not e.np. Red locally before: 1 failed, 68 passed; after: 69 passed. Benchmarks use no numpy. The ubuntu fdiv/mod failures are separate (libm flags) and tracked in their own issue.