MAINT: Mark npy_memchr with no_sanitize("alignment") on clang
#21475
Conversation
This file contains 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
Clangs sanitizer reports unaligned access here, which is correct but intentional. It may well be that the code would be better of trying to avoid this unaligned access (and rather vectorizing harder). But, this is a bit of a tricky choice, since we have to optimize for different use-cases (in particular very short scans may be interesting). So changing this would best be done together with some more careful benchmarks. See also numpygh-21117, which introduced manual loop unrolling to avoid the unaligned access. Closes numpygh-21116
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.
Backport of #21467.
Clangs sanitizer reports unaligned access here, which is correct
but intentional. It may well be that the code would be better of
trying to avoid this unaligned access (and rather vectorizing harder).
But, this is a bit of a tricky choice, since we have to optimize for
different use-cases (in particular very short scans may be interesting).
So changing this would best be done together with some more careful
benchmarks.
See also gh-21117, which introduced manual loop unrolling to avoid the
unaligned access.
Closes gh-21116